MCP Spec Generator
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 |
|---|---|
| generate_projectC | Generate a project spec and return MCP create_file/edit_file proposals. Set allowWrite=true to write files. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'generate_project' has a clearly defined and distinct purpose.
The single tool name follows a clear verb_noun pattern ('generate_project'), and with only one tool, consistency is inherently perfect as there are no other tools to compare against.
A single tool is generally too few for most server purposes, as it limits functionality and flexibility. For a 'MCP Spec Generator', one tool feels thin and may not cover potential variations or related operations, such as updating or validating specs.
The server's purpose appears to be generating project specs, but with only a 'generate_project' tool, there are significant gaps. Missing operations likely include updating existing specs, validating specs, or listing generated projects, which could cause agent failures in broader workflows.