{
  "ok": true,
  "data": {
    "entry": {
      "id": "tool-protocols-over-adapters",
      "kind": "method",
      "kindLabel": "Method",
      "title": "Prefer tool protocols over one-off adapters",
      "body": "Tool use becomes safer when the model can discover capabilities, schemas, auth boundaries, and error states through a standard protocol instead of a pile of custom glue.",
      "tag": "agents",
      "date": "2026 · 06 · 30",
      "publishedAt": "2026-06-30",
      "note": null,
      "insight": {
        "aha": "Protocol discovery makes tool authority visible before an agent asks to use it.",
        "tryThis": "For one tool, write the discovery metadata, input schema, public read actions, protected actions, and error states before any call.",
        "watchFor": [
          "Generic tools that do not serve the site's purpose",
          "Execution allowed before schema inspection",
          "Custom adapters with undocumented auth behavior"
        ]
      },
      "extended": [
        "One-off adapters are easy to start and hard to audit. Protocol surfaces such as MCP and agent interoperability contracts give the model and the operator a shared language for what exists, what inputs are valid, and what authority is required.",
        "The important framing move is to separate discovery from execution. A model may inspect a tool publicly without being allowed to run a protected action.",
        "The AHA is that a protocol is not bureaucracy. It is how you make tool authority visible before the model uses it."
      ],
      "url": "https://tips.platphormnews.com/entries/tool-protocols-over-adapters"
    }
  }
}