2 posts tagged with "Integrations"

"What can your agent do?" is two questions wearing one coat. The first is about the action space: once the agent is awake and thinking, what can it reach, call, read, and change? The second is about the trigger space: what makes it wake up in the first place? Teams conflate them constantly, and the conflation is expensive, because the two want opposite answers.

There's a tidy argument going around: skip the Model Context Protocol, just give the agent a shell and a CLI. No server to run, no schemas to maintain, and — the clincher — it saves tokens, because a command is short and a tool definition is long. It's a good argument. It's also only half right, and the missing half is where most of the cost actually lives.