Prompt Refiner MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind the HTTP server to (default: 0.0.0.0) | 0.0.0.0 |
| PORT | No | Port to bind the HTTP server to (default: 8000) | 8000 |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_schemaA | Return the JSON schema for a deterministic prompt brief. |
| validate_briefC | Validate a prompt brief and report its completeness score. |
| build_prompt_variantsC | Build focused, detailed, and structured prompt variants without calling an LLM. |
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 3 tools
Each tool has a clearly distinct purpose: retrieving the schema, validating a brief, and generating prompt variants. There is no meaningful overlap or ambiguity between them.
All tool names follow a consistent verb_noun snake_case pattern: get_schema, validate_brief, build_prompt_variants. The naming is predictable and uniform.
Three tools is a reasonable, focused count for a narrow domain like prompt refining. Each tool serves a distinct step in the workflow without unnecessary bloat.
The toolset covers the full core workflow: understanding the schema, validating input, and producing the deliverable. No obvious missing operations are needed for the stated purpose.