Merge pull request modelcontextprotocol#48 from modelcontextprotocol/justin/fix-cancelled-method

Fix the `cancelled` notification name

Author: jspahrsummers

docs/spec/cancellation.md

@@ -8,7 +8,7 @@ MCP supports request cancellation through a dedicated notification message. This
 
 ## Cancellation Protocol
 
-When a party wants to cancel a request, they send a `cancelled` notification containing the ID of the request they wish to cancel:
+When a party wants to cancel a request, they send a "cancelled" notification containing the ID of the request they wish to cancel:
 
 For example, initiating a request:
 
@@ -28,7 +28,7 @@ For example, initiating a request:
 ```json
 {
   "jsonrpc": "2.0",
-  "method": "cancelled",
+  "method": "notifications/cancelled",
   "params": {
     "requestId": "abc123",
     "reason": "User interrupted operation"

schema/schema.json

@@ -91,7 +91,7 @@
             "description": "This notification can be sent by either side to indicate that it is cancelling a previously-issued request.\n\nThe request SHOULD still be in-flight, but due to communication latency, it is always possible that this notification MAY arrive after the request has already finished.\n\nThis notification indicates that the result will be unused, so any associated processing SHOULD cease.\n\nA client MUST NOT attempt to cancel its `initialize` request.",
             "properties": {
                 "method": {
-                    "const": "cancelled",
+                    "const": "notifications/cancelled",
                     "type": "string"
                 },
                 "params": {

schema/schema.ts

@@ -125,7 +125,7 @@ export type EmptyResult = Result;
  * A client MUST NOT attempt to cancel its `initialize` request.
  */
 export interface CancelledNotification extends Notification {
-  method: "cancelled";
+  method: "notifications/cancelled";
   params: {
     /**
      * The ID of the request to cancel.