dev-prompt-mcp
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reload_promptsA | 重新加载所有预设的prompts |
| get_prompt_namesB | 获取所有可用的prompt名称 |
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 2 tools
The two tools, get_prompt_names and reload_prompts, have clearly distinct purposes: one retrieves names, the other reloads prompts. There is no overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern in snake_case, making them predictable and easy to understand.
With only 2 tools, the set is on the lower end of appropriate. It feels thin for a prompt management server, which typically would have more operations, but it could be a minimal interface for simple listing and reloading.
The tool surface lacks essential operations for prompt management, such as retrieving prompt content, creating, updating, or deleting prompts. Agents cannot perform basic CRUD tasks, leading to significant gaps.