#mcp
Every post tagged "mcp".
7 posts · showing 1–7
-
Lock-In Risk in Agent Tooling, and How to Keep Optionality
The API call is trivially portable — the coupling forms in four other places, and the worst one isn't technical at all. One question tells you how exposed you are.
-
Will Open-Source Harnesses Eat Commercial Coding Tools?
The premise is right — the loop is a few hundred lines. The conclusion is too fast, because the loop isn't the product, and one of the real advantages is invisible from outside.
-
The Tool That Changed Under You: Supply-Chain Risk in Agent Tooling
No deploy, no prompt edit, and an ops agent started restarting services mid-investigation. A maintainer had improved a tool's documentation — and documentation, in an agent, is instruction.
-
Designing Tools for Agents vs Designing APIs for Developers
One endpoint, one tool is the obvious mapping and the wrong one. APIs assume a consumer who reads docs once and writes a loop — an agent re-decides everything from a paragraph, every call.
-
MCP: What a Standard Tool Protocol Changes, and What It Doesn't
Portable integrations and runtime discovery are real wins. Tool design, selection accuracy, permissions, and untrusted content are exactly as hard as before — and easy connection quietly makes two of them worse.
-
Framework or Plain Loop? Four Questions That Actually Decide It
The core agent loop is under a hundred lines — that's never what a framework saves you. Four situational questions decide it, and the one about 3am debugging should carry the most weight.
-
Your Tool Description Is a Prompt: Rewriting Schemas the Model Can Actually Follow
A three-word tool description sent an inbox agent after the wrong thread. Tool specs live inside the prompt, and five specific rewrites to yours will fix more wrong calls than any system-prompt rule.