Skip to main content
Glama
Sign In
PMFlow MCP

PMFlow MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

export_markdown_specs

Exports structured PRD and story backlog data from PMFlow MCP into standardized Markdown documentation for sharing or review.

Instructions

Exports structured PRD and story backlog into standardized Markdown documentation.

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

Input Schema

NameRequiredDescriptionDefault
prdNoOptional PRD dict generated by generate_prd
storiesNoOptional list of story dicts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.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 provided, so the description carries the full burden of behavioral disclosure. It discloses the output format (Markdown) but does not say whether it writes a file, returns content, overwrites existing documentation, requires permissions, or how errors are handled.

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?

A single front-loaded sentence with no filler; every phrase contributes to stating the action and output format.

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?

With no annotations and no output schema, the one-sentence description does not explain the return value, destination, or side effects of exporting. For a tool with nested optional objects, it leaves too much unspecified for reliable invocation.

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 both optional parameters. The description broadly maps 'PRD and story backlog' to prd/stories but adds no extra meaning about optionality or what happens when either parameter is omitted, so the baseline of 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 ('Exports') and resources ('structured PRD and story backlog') plus the output format ('standardized Markdown documentation'). It is distinguishable from siblings such as generate_prd and decompose_stories because it exports rather than generates, though it does not explicitly name alternatives.

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 gives no when-to-use, when-not-to-use, or alternative guidance. The only hint is in the schema descriptions noting that prd may come from generate_prd, but that does not guide invocation choices or prerequisites.

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

Deploy Server

Other Tools