Skip to main content
Glama

Update Prd

update_prd

Create or update PRD, VISION, SCOPE, or REQUIREMENTS markdown documents in a project root to keep product planning files current.

Instructions

Create or update a PRD document (PRD, VISION, SCOPE, REQUIREMENTS).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "document": "<document>",
      "content": "<content>"
    },
    "name": "update_prd"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoProject root directory..
contentYesThe full markdown content of the document.
documentYesWhich document to write — PRD, VISION, SCOPE, or REQUIREMENTS.

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 behavioral burden. "Create or update" implies overwrite of existing content, but it never states whether the full document is replaced, whether an existing file is preserved or destroyed, or whether any precondition (existing project root) is required. With an output schema present, return values need not be described, but mutation semantics are a real gap.

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?

A single front-loaded sentence with the verb first and no filler. The parenthetical value list is slightly redundant with the schema but is genuinely useful for quick scanning.

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

Completeness3/5

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

With 100% schema coverage and an output schema, the main remaining need is behavioral context around a mutation tool: overwrite behavior, relation to the sibling file-write tools, and prerequisites. The description covers purpose but leaves those unresolved.

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 schema already documents path, content, and document. The description's enumeration of PRD/VISION/SCOPE/REQUIREMENTS duplicates the document parameter description and adds no new meaning about content format or path resolution. Baseline 3 applies since the 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 names a clear verb pair ("Create or update") and a specific resource ("PRD document"), and enumerates the four document types the tool manages. It is distinguishable from read-oriented siblings like get_prd and summarize_prd, though it never names them explicitly.

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 when-to-use guidance: nothing says whether this should be preferred over the generic write_file for the same path, or when to use update_prd versus edit_file for a small change. The only implied guidance comes from the document-type parenthetical.

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