To add to this, MCPs usually focus on capabilities. This is especially useful in multi-hop situations.
As an illustration, lets say I ask the agent to “Read the issue Bob posted today from Linear (issue tracker), pull relevant logs from DataDog (log tool) and suggest a fix”
In the MCP world, my agent doesn’t have to spend tokens / time understanding APIs or the protocol (as the parent comment suggests). Instead, it relies on the tool provider for the best way to “read the issue” or “pull logs”.
Same thing, in the API world, would usually involve multiple API hits (and possibly using the wrong APIs or params for them), interpreting the results and hitting few more APIs again.
My biggest problem is that msps can't be chained together and that the response schema is not know models are very good at filtering with jq to get only the relevant fields
Comments
To add to this, MCPs usually focus on capabilities. This is especially useful in multi-hop situations.
As an illustration, lets say I ask the agent to “Read the issue Bob posted today from Linear (issue tracker), pull relevant logs from DataDog (log tool) and suggest a fix”
In the MCP world, my agent doesn’t have to spend tokens / time understanding APIs or the protocol (as the parent comment suggests). Instead, it relies on the tool provider for the best way to “read the issue” or “pull logs”.
Same thing, in the API world, would usually involve multiple API hits (and possibly using the wrong APIs or params for them), interpreting the results and hitting few more APIs again.
My biggest problem is that msps can't be chained together and that the response schema is not know models are very good at filtering with jq to get only the relevant fields