Prompts
Interaction templates predefined by an MCP Server, used to guide users in initiating requests in a particular manner and to standardize the interaction flow.
Core Facts
MCP defines three core primitives: Tools (tool invocation), Resources (resource reading), and Prompts (prompt templates).
The model decides when to invoke tools, the client or user chooses which resources to read, and prompts are usually triggered explicitly by the user; this division shapes permission design.
Timeline (last 90 days)
The model decides when to invoke tools, the client or user chooses which resources to read, and prompts are usually triggered explicitly by the user; this division shapes permission design.
For any operation involving money, identity, or security, it is not sufficient to rely solely on prompts to constrain the model — enforcement must be mandatory at the code level through hooks, because hooks are guarantees while prompts are merely suggestions.
An analysis guide is a Prompt — a reusable message template that provides repeatable guidance
All Facts (4)
MCP defines three core primitives: Tools (tool invocation), Resources (resource reading), and Prompts (prompt templates).
90%VerifiedThe model decides when to invoke tools, the client or user chooses which resources to read, and prompts are usually triggered explicitly by the user; this division shapes permission design.
65%UnverifiedFor any operation involving money, identity, or security, it is not sufficient to rely solely on prompts to constrain the model — enforcement must be mandatory at the code level through hooks, because hooks are guarantees while prompts are merely suggestions.
50%UnverifiedAn analysis guide is a Prompt — a reusable message template that provides repeatable guidance
50%