Method2026-06-30#agents

Prefer tool protocols over one-off adapters

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.

Aha moment

Protocol discovery makes tool authority visible before an agent asks to use it.

Try this

For one tool, write the discovery metadata, input schema, public read actions, protected actions, and error states before any call.

Open NotesEntry JSON

Watch for

  • Generic tools that do not serve the site's purpose
  • Execution allowed before schema inspection
  • Custom adapters with undocumented auth behavior