Prompts MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_promptC | Add a new prompt to the collection |
| get_promptC | Retrieve a prompt by name |
| list_promptsB | List all available prompts |
| delete_promptC | Delete a prompt by name |
| create_structured_promptC | Create a new prompt with guided metadata structure |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: add_prompt and create_structured_prompt differ in metadata handling, while delete_prompt, get_prompt, and list_prompts each target a specific operation on prompts. An agent can easily distinguish between them.
All tools follow a consistent verb_noun pattern in snake_case (e.g., add_prompt, delete_prompt, list_prompts). The naming is predictable and uniform throughout the set, making it easy for agents to parse.
With 5 tools, this server is well-scoped for managing prompts, covering core operations (create, read, list, delete) without being too sparse or bloated. Each tool serves a clear purpose in the domain.
The toolset provides solid CRUD coverage (add/create, get, list, delete) for prompts, but lacks an update or edit tool, which could be a minor gap for modifying existing prompts. However, agents can work around this by deletion and recreation.