This topic was automatically generated from Slack. You can find the original thread here.
Could it be the case that the outlook servers (Microsoft Outlook Calendar MCP Server | Pipedream and Microsoft Outlook MCP Server | Pipedream) are not made the right way according to the mcp standard? Every client I’m trying to call tools with struggles with the odata/msft graph params. Curious to hear your thoughts around it
Can you elaborate / provide some examples?
Yes so there is a single ‘instructions’ box for natural language input - see screenshot. Shouldn’t we via json/rpc return the data in a way that the agent when fetching the available tools sees with which params he needs to call the tool with? Or if this ‘instruction’ based approach is made on purpose, curious to hear the considerations (e.g. are you expecting on par accuracy when llms improve so that you don’t need to specify the params anymore + no latency tradeoffs anymore).
Check out our docs here for some more info and context: https://pipedream.com/docs/connect/mcp/developers/#tool-modes
Wow gamechanger. So good you support the tools-only mode. it works so much faster and way more accurate. Thanks for pointing me to the right docs !
