1. Agents don't know the APIs. This is a way for you to declare them.
2. You get to decide what functionality you want to expose agents to.
3. An API enables reliable tool use.
The APIs have docs. The agent can go read them and build against them.
The agent doesn't know what tools are available on your host. And searching for the documentation is slower and less reliable. It's an optimization.
the guiding promise of AI was able to figure out unstructured data. Manually crafting prompts and description examples for tools is a step orthogonal to progress. Searching for docs, great now you have 1000 tools saying they do same thing exposed to model, now we need another search on top of that?
yeah - I don't get it. I'm all for abstraction but the entire point of using agents at the UX-level is you didn't need a single agreed-upon protocol to make it work. Feels like they're using the old Microsoft fire and motion strategy to keep people busy on their tech, or artificially introduce structure & coupling that - suprise - benefits the maker of shovels, not the diggers.
> In infantry battles, he told us, there is only one strategy: Fire and Motion. You move towards the enemy while firing your weapon. The firing forces him to keep his head down so he can’t fire at you.
shhhh - that's the big announcement for next year - the "Agnostic" General Interface (AGI) ... works with any endpoint no more lengthy MCP or A2A setup!
you are too late already... there are now mcp servers that wrap other mcp servers in a single mcp interface... mmcp