Expand description
Answering a server’s request for input (SEP-2322, 2026-07-28).
A server cannot send a request of its own at this revision, so a call that
needs the user answers with an InputRequiredResult: resultType: "input_required", the questions in inputRequests, and optionally a
requestState of its own. The client answers by retrying the original
request with inputResponses keyed as the questions were, echoing
requestState back unchanged — and sending none when the server sent none.
Every retry is a new JSON-RPC request with a new id.
https://modelcontextprotocol.io/specification/2026-07-28/basic/patterns/mrtr
This works on any method the SEP names (tools/call, prompts/get,
resources/read) and over any ClientTransport, handshake or not.
Structs§
- Input
Answers - What a client answers an
InputRequiredResultwith.
Constants§
- MAX_
INPUT_ ROUNDS - How many times a call may be retried with fresh input before it fails.
Traits§
- Input
Resolver - Answers one input request.
Functions§
- answer_
input_ required - Answers
resultif it is an interimInputRequiredResult. - call_
resolving - Sends
methodwithparams, answering input requests throughresolve.