MCP servers now support response data filtering using jq

Previously, large API responses could be a big problem for MCP servers - it would eat up LLM context windows with lots of irrelevant data, when a small subset may be sufficient to answer the user’s query.  Manually excluding some response data in the MCP server can alleviate that problem, but then it makes some data inaccessible by the LLM.

To solve this problem, our MCP servers now provide an additional jq_filter parameter on each tool call, which allows the LLM to automatically use jq syntax to transform the API response based on the response schema.

This means that the LLM can dynamically select only the information it wants to answer the user’s query, while at the same time not restricting the data that is possible to access via the MCP server.

This functionality is automatically available in all MCP servers now.

‍