change 'decline' to 'reject' in elicitation

Author: bhosmer-ant

docs/development/roadmap.mdx

@@ -5,7 +5,7 @@ description: Our plans for evolving Model Context Protocol
 
 <Info>Last updated: **2025-03-27**</Info>
 
-The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and direction for approximately **the next six months**, though these may change significantly as the project develops. To see what's changed recently, check out the \*_[specification changelog](/specification/2025-06-18/changelog/)_.
+The Model Context Protocol is rapidly evolving. This page outlines our current thinking on key priorities and direction for approximately **the next six months**, though these may change significantly as the project develops. To see what's changed recently, check out the **[specification changelog](/specification/2025-06-18/changelog/)**.
 
 <Note>
 

docs/specification/2025-06-18/client/elicitation.mdx

@@ -37,7 +37,7 @@ Applications **SHOULD**:
 
 - Provide UI that makes it clear which server is requesting information
 - Allow users to review and modify their responses before sending
-- Respect user privacy and provide clear decline and cancel options
+- Respect user privacy and provide clear reject and cancel options
 
 </Warning>
 
@@ -151,14 +151,14 @@ To request information from a user, servers send an `elicitation/create` request
 }
 ```
 
-**Decline Response Example:**
+**Reject Response Example:**
 
 ```json
 {
   "jsonrpc": "2.0",
   "id": 2,
   "result": {
-    "action": "decline"
+    "action": "reject"
   }
 }
 ```
@@ -290,7 +290,7 @@ Elicitation responses use a three-action model to clearly distinguish between di
   "jsonrpc": "2.0",
   "id": 1,
   "result": {
-    "action": "accept", // or "decline" or "cancel"
+    "action": "accept", // or "reject" or "cancel"
     "content": {
       "propertyName": "value",
       "anotherProperty": 42
@@ -306,10 +306,10 @@ The three response actions are:
    - The `content` field contains the submitted data matching the requested schema
    - Example: User clicked "Submit", "OK", "Confirm", etc.
 
-2. **Decline** (`action: "decline"`): User explicitly rejected the request
+2. **Reject** (`action: "reject"`): User explicitly rejected the request
 
    - The `content` field is typically omitted
-   - Example: User clicked "Decline", "Reject", "No", etc.
+   - Example: User clicked "Reject", "Decline", "No", etc.
 
 3. **Cancel** (`action: "cancel"`): User dismissed without making an explicit choice
    - The `content` field is typically omitted
@@ -318,7 +318,7 @@ The three response actions are:
 Servers should handle each state appropriately:
 
 - **Accept**: Process the submitted data
-- **Decline**: Handle explicit rejection (e.g., offer alternatives)
+- **Reject**: Handle explicit rejection (e.g., offer alternatives)
 - **Cancel**: Handle dismissal (e.g., prompt again later)
 
 ## Security Considerations

docs/specification/draft/client/elicitation.mdx

@@ -37,7 +37,7 @@ Applications **SHOULD**:
 
 - Provide UI that makes it clear which server is requesting information
 - Allow users to review and modify their responses before sending
-- Respect user privacy and provide clear decline and cancel options
+- Respect user privacy and provide clear reject and cancel options
 
 </Warning>
 
@@ -151,14 +151,14 @@ To request information from a user, servers send an `elicitation/create` request
 }
 ```
 
-**Decline Response Example:**
+**Reject Response Example:**
 
 ```json
 {
   "jsonrpc": "2.0",
   "id": 2,
   "result": {
-    "action": "decline"
+    "action": "reject"
   }
 }
 ```
@@ -290,7 +290,7 @@ Elicitation responses use a three-action model to clearly distinguish between di
   "jsonrpc": "2.0",
   "id": 1,
   "result": {
-    "action": "accept", // or "decline" or "cancel"
+    "action": "accept", // or "reject" or "cancel"
     "content": {
       "propertyName": "value",
       "anotherProperty": 42
@@ -306,10 +306,10 @@ The three response actions are:
    - The `content` field contains the submitted data matching the requested schema
    - Example: User clicked "Submit", "OK", "Confirm", etc.
 
-2. **Decline** (`action: "decline"`): User explicitly rejected the request
+2. **Reject** (`action: "reject"`): User explicitly rejected the request
 
    - The `content` field is typically omitted
-   - Example: User clicked "Decline", "Reject", "No", etc.
+   - Example: User clicked "Reject", "Decline", "No", etc.
 
 3. **Cancel** (`action: "cancel"`): User dismissed without making an explicit choice
    - The `content` field is typically omitted
@@ -318,7 +318,7 @@ The three response actions are:
 Servers should handle each state appropriately:
 
 - **Accept**: Process the submitted data
-- **Decline**: Handle explicit rejection (e.g., offer alternatives)
+- **Reject**: Handle explicit rejection (e.g., offer alternatives)
 - **Cancel**: Handle dismissal (e.g., prompt again later)
 
 ## Security Considerations

schema/draft/schema.json

@@ -1371,10 +1371,10 @@ export interface ElicitResult extends Result {
   /**
    * The user action in response to the elicitation.
    * - "accept": User submitted the form/confirmed the action
-   * - "decline": User explicitly declined the action
+   * - "reject": User explicitly rejected the action
    * - "cancel": User dismissed without making an explicit choice
    */
-  action: "accept" | "decline" | "cancel";
+  action: "accept" | "reject" | "cancel";
 
   /**
    * The submitted form data, only present when action is "accept".