Skip to main content
Glama
Njengah

PRD Generator MCP Server

by Njengah

generate_prd_from_readme

Convert README files into structured Product Requirements Documents (PRDs) to streamline documentation processes and save time.

Instructions

Generate a PRD from a README file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
readme_pathYesPath to README file

Implementation Reference

  • The main handler logic for the 'generate_prd_from_readme' tool. It reads the README file content using fs.readFile, constructs a PRD markdown template by incorporating parts of the README and fixed sections, and returns it as text content in the expected MCP format.
      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}`);
        }
      }
  • The input schema defining the expected arguments for the tool: an object with a required 'readme_path' string property.
    inputSchema: {
      type: "object",
      properties: {
        readme_path: {
          type: "string",
          description: "Path to README file",
        },
      },
      required: ["readme_path"],
    },
  • server/index.js:26-43 (registration)
    The tool registration in the ListTools response, including name, description, and input schema.
        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?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions generation but doesn't specify what a PRD entails, whether it modifies files, requires specific permissions, or has rate limits. This leaves significant gaps for a tool that presumably creates output.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool.

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?

For a generation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a PRD is, what format it outputs, or any behavioral traits like file creation or permissions needed, leaving the agent with incomplete context.

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?

Schema description coverage is 100%, so the input schema already documents the single parameter 'readme_path' fully. The description adds no additional meaning about parameters beyond what's in the schema, meeting the baseline score when schema does the heavy lifting.

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 a PRD') and the resource ('from a README file'), making the tool's purpose immediately understandable. However, without sibling tools to differentiate from, it cannot achieve a perfect score of 5 for explicit sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without context about appropriate scenarios or limitations.

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