Skip to main content
Glama
Njengah

PRD Generator MCP Server

by Njengah

generate_prd_from_readme

Generate a structured Product Requirements Document (PRD) from a README file by providing its path, automating documentation creation.

Instructions

Generate a PRD from a README file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readme_pathYesPath to README file

Implementation Reference

  • The main handler for the 'generate_prd_from_readme' tool. Reads a README file from the given path and generates a PRD template with basic project overview, description (first 5 lines), key features, technical requirements, and generation timestamp. Throws an error if the README file cannot be read.
      if (name === "generate_prd_from_readme") {
        try {
          const readmeContent = await fs.readFile(args.readme_path, "utf-8");
    
          const prdTemplate = `
    # Product Requirements Document
    
    ## Project Overview
    Based on: ${args.readme_path}
    
    ## Description
    ${readmeContent.split("\n").slice(0, 5).join("\n")}
    
    ## Key Features
    - Feature extraction from README
    - Automated PRD generation
    - Time-saving documentation
    
    ## Technical Requirements
    - Node.js runtime
    - File system access
    - README file parsing
    
    Generated on: ${new Date().toISOString()}
          `;
    
          return {
            content: [
              {
                type: "text",
                text: prdTemplate,
              },
            ],
          };
        } catch (error) {
          throw new Error(`Failed to read README: ${error.message}`);
        }
      }
    
      throw new Error(`Unknown tool: ${name}`);
    });
  • Input schema for the 'generate_prd_from_readme' tool. Requires one parameter: 'readme_path' (string) specifying the path to the README file.
    inputSchema: {
      type: "object",
      properties: {
        readme_path: {
          type: "string",
          description: "Path to README file",
        },
      },
      required: ["readme_path"],
    },
  • server/index.js:24-43 (registration)
    Registration of the 'generate_prd_from_readme' tool via ListToolsRequestSchema handler. The tool is named 'generate_prd_from_readme' with description 'Generate a PRD from a README file'.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          {
            name: "generate_prd_from_readme",
            description: "Generate a PRD from a README file",
            inputSchema: {
              type: "object",
              properties: {
                readme_path: {
                  type: "string",
                  description: "Path to README file",
                },
              },
              required: ["readme_path"],
            },
          },
        ],
      };
    });
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description must disclose behavioral traits. It does not mention any side effects, error conditions, or output characteristics, leaving the agent uninformed about the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise, using a single sentence. It is not verbose, but could be slightly more informative without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and annotations, the description is insufficient. It does not explain what the generated PRD contains, any constraints, or how the README is processed, leaving significant gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the parameter 'readme_path' described. The tool description does not add extra meaning beyond the schema, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (Generate) and the resource (PRD from a README file). It is specific enough to understand the tool's function, though it lacks details about the PRD format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. Since there are no sibling tools, the need is lower, but the description offers no context for appropriate use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Njengah/prd-dxt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server