◈OpenTree DashboardSign in

$ date -I # 2026-07-25

MCP has three primitives, and the difference is who decides to invoke them

Most confusion about the three MCP primitives comes from comparing them by shape — they all end with your server returning something. Compare them by who initiates and the choice becomes almost mechanical.

The distinction is control

Tools are invoked by the model, so they may have side effects and the model must be able to decide when. Resources are read by the client, usually to put context in front of the model, and must therefore be safe to read at any time. Prompts are chosen by the user — a named workflow that pre-loads instructions.

Side by side

ToolResourcePrompt
Invoked byThe modelThe clientThe user
May have side effectsYesNoNo
Typical contentAn actionData or documentsInstructions
Identified byA name and a schemaA URIA name
Seen by the user asA call the model madeContextA menu item

When to reach for each

The trap: read-only tools

The common mistake is a read-only tool where a resource belongs — get_site as a tool rather than the site as a resource. It works, and it costs you: the model has to decide to call it, so it often does not, and when it does it burns a turn. A resource can just be there.

The opposite mistake is worse. Anything with a side effect exposed as a resource can be triggered by a client that is merely gathering context. Read-safety is the contract.

A publish-shaped server, sorted

Applying the rule here: the twelve verbs are tools, because each changes something or reads something the model specifically asked for. Documents that describe the deployment — the endpoint list, the defaults, the page index at /llms.txt — are resource-shaped, and are published as plain HTTP so any client can read them whether or not it implements the resource primitive.

Not every client implements all three

Tool support is universal; resources and prompts are patchier, and the gap moves. The practical consequence: if a capability is essential, expose it as a tool, because that is the primitive you can rely on. Use the other two to make life nicer for clients that have them.

Can the same thing be both a tool and a resource?

Yes, and for read-only data that is often pragmatic while client support is uneven. Keep the behaviour identical so the model cannot tell which door it came through.

Do resources have to be text?

No — a resource has a URI and a MIME type. Text and JSON dominate because that is what a model can act on.

Which does this deployment expose?

Twelve tools, plus discovery and description documents over plain HTTP. The verbs are where the value is, and they are the primitive every client can call.

Are prompts worth implementing?

Only if the workflow is genuinely multi-step and users repeat it. Otherwise it is a menu item duplicating what the model would have done anyway.

Keep reading