Core
Prompt
Learn what MCP prompts are, how they package reusable workflows, and when to use prompts with generated MCP tools.
Definition
A prompt is a reusable interaction template exposed by an MCP server. Prompts help clients start a task with structured instructions, expected arguments, and context rather than forcing each user or agent to invent the workflow from scratch.
How Astrail Uses It
Astrail-generated docs and SDK bundles can describe recommended prompts for common operations, while hosted endpoints keep the actual execution path inside tools and endpoint maps.
Implementation Checklist
Use prompts to package repeatable workflows, not to bypass tool authorization.
Keep prompt arguments explicit and validated.
Link prompts to the tools and resources they expect to use.
Avoid embedding secrets or tenant-specific values in reusable prompts.
FAQ
Are prompts required for an MCP server?
No. Prompts are optional. Many production servers start with tools only, then add prompts for common workflows once usage patterns are clear.
Can prompts call tools directly?
Prompts describe a workflow for the client and model. Tool calls still happen through the MCP tool invocation path, where validation and authorization should be enforced.