vibe-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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| optimize_promptD | – |
| score_promptD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vibe-optimize |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools, score_prompt and optimize_prompt, suggest distinct actions, though the lack of descriptions leaves some room for overlap. An agent could generally tell them apart by verb alone.
Both tool names follow the same lowercase snake_case verb_noun pattern: score_prompt and optimize_prompt. The naming is fully consistent.
With only two tools, the server feels minimal and near the thin end of the acceptable range. It could be sufficient for a narrowly scoped prompt-tuning server, but the purpose is unclear without descriptions.
The surface covers scoring and optimizing prompts but lacks obvious supporting operations such as generation, comparison, or iteration. The missing descriptions also make it hard to confirm that the intended workflow is fully covered.