3 ms·
OpenAPI definitions are verbose and exhaustive. In MCPs you can remove a lot of extra material, saving tokens. For example in [1], whole `responses` schema can
by pcwelder 1y ago
OpenAPI definitions are verbose and exhaustive. In MCPs you can remove a lot of extra material, saving tokens.
For example in [1], whole `responses` schema can be eliminated. The error texts can instead be surfaced when they appear. You also don't need duplicate json/xml/url-encoded input formats.
Secondly, whole lot of complexities are eliminated, arbitrary data can't be sent and received. Finally, the tool output are prompts to the model too, so you can leverage the output for better accuracy, which you can't do with general purpose apis.
[1] https://github.com/swagger-api/swagger-petstore/blob/master/src/main/resources/openapi.yaml https://github.com/swagger-api/swagger-petstore/blob/master/...
- hn_throwaway_99 1y agoSo why can't the LLM just take the verbose OpenAPI spec, summarize it and remove the unnecessary boilerplate and cruft (do that once), and only use the summarized part in the prompt?
- 0x457 1y agoThere is probably an MCP for that