#MCP

My MCP Server Had 39 Tools. I Had Designed It for the Wrong Caller.

SWCraft grew to 39 MCP tools by exposing model operations one tool at a time. Separating the software API from the agent interface reduced the surface to 13 without removing capability.

Nothing Changed in the API. Everything Changed for the Agent.

An MCP tool schema explains how to call a function, but not when that function should become a candidate. A task-scoped semantic contract can keep a growing tool catalog behaviorally compatible.

An Agent Can Pass Validation and Still Make an Unsafe Change

The agent was authorized to modify one component. It helpfully modified two. The model still validated. Why MCP capability is not task authority, and how a task-scoped mutation boundary closes the gap.

My Two AI Agents Talk MCP to Each Other. There Is No Standalone Tool Server.

The default MCP story is one fat tool server, many clients. When I needed two of my domain agents to talk to each other, that shape was the wrong one — and the alternative shows what MCP is actually good for.