Skip to main content
Glama

Extract Requirements

extract_requirements

Parses PRD markdown files to extract structured requirements and saves them to requirements.json, turning product documents into actionable project data.

Instructions

Parse PRD markdown files to extract structured requirements and save them into requirements.json.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It implies a write (saving requirements.json) but says nothing about whether an existing requirements.json is overwritten or merged, what happens if no PRD is found, or whether the write is reversible — all material for a mutating tool with zero annotation coverage.

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?

One clean sentence, front-loaded with the action and ending with the concrete artifact produced. No filler, though the brevity is partly a symptom of missing information rather than disciplined economy.

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

Completeness4/5

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

An output schema exists, so return-value explanation is not required, and the description covers the essential input-to-output transformation. The gaps are the meaning of 'path' and the overwrite/merge semantics of requirements.json, which are meaningful for a mutating tool.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'path' parameter defaults to '.', yet the description never clarifies whether path is a file, a directory, or a project root, nor how the PRD file is located within it. With 0% coverage the description needed to compensate and does not.

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 gives a specific verb chain (parse -> extract -> save), names the input artifact (PRD markdown files), and names the output artifact (requirements.json). That distinguishes it reasonably well from siblings like verify_requirements or summarize_prd, though it never explicitly says how it differs from them.

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?

There is no guidance on when to call this versus get_prd, update_prd, summarize_prd, or verify_requirements, nor on prerequisites such as a PRD existing or being in a particular location. The agent must infer all triggering conditions from the one-line purpose statement.

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