Bug: `request-start` message not respected for MCP Tool calls
I've set this both through the API and through the UI and get the same results.
The same default "just a sec", "one moment", or whatever is played.
Repro steps:
Create assistant
Create and assign MCP tool to assistant that includes a custom
Trigger an MCP call through the conversation (I made a toy "lookup-weather" tool for this)
Note that no matter what is specified in the
My MCP calls are fast, so I'd like to assign no
The same default "just a sec", "one moment", or whatever is played.
Repro steps:
Create assistant
Create and assign MCP tool to assistant that includes a custom
request-start message.Trigger an MCP call through the conversation (I made a toy "lookup-weather" tool for this)
Note that no matter what is specified in the
request-start message, it is not respected. The default behavior is still used.My MCP calls are fast, so I'd like to assign no
request-start message and add a message for >500ms response time, but it doesn't seem like that's an option.
