json-promptor-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 |
|---|---|
| convert_prompt_to_jsonA | Convert a raw text prompt into a structured JSON prompt with extracted fields (purpose, goal, audience, context, tone, instructions, format) |
| edit_prompt_jsonB | Edit a field in an existing structured JSON 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 are clearly distinct: one converts raw text to a structured JSON prompt, the other edits an existing JSON prompt. There is no ambiguity or overlap.
Both tools follow the verb_noun pattern consistently: convert_prompt_to_json and edit_prompt_json. The naming is clear and predictable.
With only 2 tools, the server is minimal but appropriately scoped for its narrow purpose of converting and editing JSON prompts. However, it could benefit from a few more tools like validation.
The tools cover the core workflow of converting raw prompts to JSON and editing them. Missing operations like validation or export are minor gaps but do not severely hinder the stated purpose.