2 ms·
Isn't that just a case of have a strong API that speak some standard like OpenAPI with sound documentation? Maybe throw the key bits into a markdown file that y
by Havoc 1y ago
Isn't that just a case of have a strong API that speak some standard like OpenAPI with sound documentation? Maybe throw the key bits into a markdown file that you can inject into the LLM
The more interesting piece to me here is what Amazon does. Their API/anti-scrapping is notoriously hostile to anyone that hasn't jumped through loads of hoops
- gavmor 1y ago"Sound documentation" becomes something like SEO for agents. Take a look at the MCP spec[0]: ``` "metadata": { "name": "My MCP", "description": "A description of my MCP", "version": "1.0.0", // Optional "author": "Your Name", // Optional "license": "MIT" // Optional } ``` ``` "tools": [ { "name": "tool_name", "description": "Tool description", "input_schema": { ... }, "output_schema": { ... } } ] ``` Each "description" attribute is an advertisement opportunity. APIs want to entice agents to select their tool. 0. https://www.mcp0.com/docs https://www.mcp0.com/docs