Skip to main content
Glama

Get Prd

get_prd

Retrieve the content of a PRD, VISION, SCOPE, or REQUIREMENTS document from a project root directory to support requirements review and planning.

Instructions

Retrieve a PRD document (PRD, VISION, SCOPE, REQUIREMENTS). Returns the content of the specified document.

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": "get_prd"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
documentNoWhich document to read — PRD, VISION, SCOPE, or REQUIREMENTS.PRD

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. 'Retrieve' and 'Returns the content' make clear this is a read operation, but it says nothing about behavior when the document does not exist, permission requirements, or whether defaults (path '.', document 'PRD') trigger implicit file resolution.

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?

Two short sentences, front-loaded with the verb and resource. The second sentence is somewhat redundant with 'Retrieve a PRD document' but is minor and clarifies the return is document content.

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?

A simple two-parameter read tool with an output schema, so return values need not be described. The definition covers what it fetches and which document types exist; only missing-file behavior and sibling differentiation remain gaps.

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 both parameters are already documented in the schema. The description repeats the valid document values but adds no meaning about path resolution, relative vs absolute paths, or what happens with missing files, so the baseline 3 applies.

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?

States a specific verb (Retrieve) and resource (PRD document) and enumerates the document types (PRD, VISION, SCOPE, REQUIREMENTS), which distinguishes it from siblings like update_prd or summarize_prd. It does not explicitly name those siblings, so it falls short of a 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description scopes the tool to PRD-family documents, which hints it should be preferred over the generic read_file for these files. There is no explicit when-to-use/when-not guidance and no mention of summarize_prd or compare_work_to_prd as alternatives.

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