Generate-Prd-Prompt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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_prd_promptC | Generate an assembled Product Requirements Document prompt with specified technology stacks and analysis focus areas |
| generate_codebase_analysis_promptC | Generate an assembled codebase analysis prompt with specified technology stacks and analysis focus areas |
| generate_bug_analysis_promptC | Generate an assembled bug analysis prompt with specified technology stacks and severity level |
| get_prd_templateA | Fetch a comprehensive Product Requirements Document markdown template with all standard sections (14 sections total) |
| get_codebase_analysis_templateB | Fetch a comprehensive codebase analysis markdown template with all standard sections (12 sections total) |
| get_bug_analysis_templateB | Fetch a comprehensive bug analysis markdown template with all standard sections (8 sections total) |
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 6 tools
Every tool has a clearly distinct purpose with no ambiguity. The 'generate' tools create prompts based on specified inputs, while the 'get' tools fetch markdown templates, and each targets a different document type (bug analysis, codebase analysis, PRD). There is no overlap in functionality between tools.
Tool names follow a consistent verb_noun pattern throughout. All tools use snake_case with 'generate' or 'get' as the verb followed by a specific noun (e.g., generate_bug_analysis_prompt, get_prd_template). This predictability makes the set easy to navigate and understand.
With 6 tools, the server is well-scoped for its purpose of generating prompts and templates for analysis and PRD documents. Each tool earns its place by covering distinct aspects (prompt generation and template fetching) across three document types, avoiding bloat while providing comprehensive coverage.
The tool surface is complete for the domain of generating prompts and templates for analysis and PRD documents. It offers CRUD-like coverage with 'generate' for creation and 'get' for retrieval, covering all three document types (bug analysis, codebase analysis, PRD) without any gaps or dead ends.