Posts tagged "mcp"
Beyond tools: MCP sampling, elicitation and tasks
MCP sampling lets servers request model calls; elicitation asks users for input; tasks track long work. Each moves control and needs its own policy.
MCP vs A2A: tools for agents versus agents talking to agents
MCP vs A2A: MCP connects an agent to tools and data, A2A connects agents to each other. Where each fits, what neither covers and why governance sits above both.
MCP authorization: OAuth 2.1, audiences and why passthrough is forbidden
MCP authorization builds on OAuth 2.1, protected resource metadata and resource indicators. How the flow works and why token passthrough is forbidden.
Tool poisoning: when the tool description is the attack
MCP tool poisoning hides instructions in tool descriptions that the model reads and users rarely see. How the attack works and how pinning and review limit it.
One MCP server per system: MCP server design you can govern
MCP server design rules for governable agents. One small server per system, namespaced tools, and read/write separation instead of one giant gateway.
Writing tools agents can actually use: names, schemas and errors
Tool design for AI agents is interface design for a model reader. A checklist for names, namespaces, narrow schemas and errors, and how small tools ease policy.
What is the Model Context Protocol? A plain explanation for platform teams
What is MCP? The Model Context Protocol standardises how an agent host finds and calls tools, resources and prompts on servers. Plain guide for platform teams
Tool, skill or prompt? Three ways to give an agent what it needs
Agent skills vs tools vs prompts: a tool acts, a skill packages know-how loaded on demand, a prompt is standing text. Includes a decision table.
Agent architecture is not application architecture: the agentix pattern
Application architecture structures code. Agent architecture decides who may do what at run time. The agentix pattern - one MCP server per system, one agent per step - is our answer.