Elicitation Timeout

[pkrc267]

Describe the bug
Timeout occurs if elicitation request isn't responded to in a second.
Inspector shows the elicitation request, but when used in AI Agent, the agent does not even show elicitation and directly gets the error.

To Reproduce
Steps to reproduce the behavior:

1. Implement elicitation for any tool, with multiple inputs
2. Test the tool in inspector
3. See the elicitation request in Elicitation tab
4. respond for 1 request, then see the error when not responded for next requests in a second or two.

error: MCP error -32001: Request timed out

Expected behavior

1. The elicitation error should be thrown to console
2. The elicitation should not timeout so quick
3. Need a timeout parameter for elicitInput function

Logs
MCP error -32001: Request timed out
error thrown at the tool response for unmet elicitation timeout

[leoni121]

@pkrc267 Which version are you using? The LATEST version of the SDK has an options parameter that can be used to pass in a timeout num

[pkrc267]

@pkrc267 Which version are you using? The LATEST version of the SDK has an options parameter that can be used to pass in a timeout num

I'm on 1.17.0
Could you share an example of how to pass that? I'm not able to find how the SDK handles the parameter passed to elicit function.

[pkrc267]

I see that in the general request method checks for a timeout in the options parameter. If nothing is provided then it goes with default 60 seconds.

typescript-sdk/src/shared/protocol.ts

Line 624 in 3dd074f

const timeout = options?.timeout ?? DEFAULT_REQUEST_TIMEOUT_MSEC;

However this further affirms the bug. Even with the default 60 seconds, the subsequent elicitation requests times-out within 2 or 3 seconds. Which should not be the case.

[garciasdos]

The same is happening to me. Even overriding this timeout option closes my connection within 2 or 3 seconds