The Hook
In JSON-RPC 2.0, omitting the id member transforms a request into a fire-and-forget notification—meaning a naive MCP server that checks id presence after routing will happily execute a state-mutating tools/call and return 202 Accepted with an empty body, leaving the AI agent blind to the mutation it just triggered.
The Deep Dive
Unlike REST, where HTTP verbs and status codes carry transport-level semantics, Model Context Protocol (MCP) multiplexes all requests and notifications over a single JSON-RPC 2.0 message stream. Per the MCP specification, notifications are strictly methods prefixed with notifications/ (such as notifications/initialized ) and must omit id , whereas every standard procedure call ( initialize , tools/list , tools/call ) must include a non-null String or Integer id .…