elicitation/create

​

Wire-level Shape

{
  "jsonrpc": "2.0",
  "id":      "srv-elicit-1",
  "method":  "elicitation/create",
  "params": {
    "message": "Which Stripe customer did you mean?",
    "requestedSchema": {
      "type": "object",
      "properties": {
        "customer_id": {
          "type":        "string",
          "description": "The Stripe customer ID",
          "enum":        ["cus_8f21", "cus_9c44", "cus_2b91"]
        }
      },
      "required": ["customer_id"]
    }
  }
}

{
  "jsonrpc": "2.0",
  "id":      "srv-elicit-1",
  "result": {
    "action":  "accept",
    "content": { "customer_id": "cus_8f21" }
  }
}

​

Schema Constraints

• type: "object" at the root
• Primitive properties of type string, number, boolean, or string with enum
• required array
• description strings (rendered as form labels and help text)

​

Capability Negotiation

"capabilities": {
  "elicitation": {}
}

​

When to Use It

• Disambiguation — multiple matches; ask the user which one
• Confirmation — destructive operations should always confirm
• Missing required context — “what date range did you mean?”

• Authentication credentials — never elicit passwords or API keys; use the server’s auth config
• Data the model could provide — if the AI can answer, let it; don’t bounce to the user for things it should figure out

​

Caveats

• Elicitation blocks the tool call until the user responds. Time out gracefully — most clients give the user 60 seconds.
• The user can decline at any point. Always have a fallback path.
• GetMCP’s built-in tools don’t elicit — this is wiring for tools you author yourself.