ProdPad MCP Server

Get ProdPad Roadmap

prodpad_get_roadmap

Read-onlyIdempotent

Retrieve a specific ProdPad roadmap by ID, including its columns and active cards, to view product plans and progress.

Instructions

Get a specific roadmap by ID with its columns and active cards.

Args:

id (string): Roadmap ID (numeric)

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": {
      "id": "<id>"
    },
    "name": "prodpad_get_roadmap"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The resource ID (numeric or UUID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered without the description. The description does add one genuinely useful behavioral detail beyond the annotations: the response includes columns and only the *active* cards, which hints at filtered/partial content. It says nothing about pagination, permissions, or error behavior when the ID is invalid.

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?

The purpose sentence is front-loaded and free of filler, and the length is appropriate for a simple single-parameter fetch. The trailing 'Args:' block duplicates the schema field and is the only slightly redundant element.

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?

With no output schema, the description carries the burden of conveying return content, and it does so adequately by naming the included columns and active cards. For a low-complexity single-parameter read tool with full annotation coverage, an agent has enough to call it correctly.

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% and there is only one parameter, so the schema already documents it. The description's 'id (string): Roadmap ID (numeric)' merely restates the schema (which even allows UUIDs, so the 'numeric' note is slightly narrower than the actual contract) and adds no real meaning.

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 states a specific verb and resource ('Get a specific roadmap by ID') and scopes the payload ('with its columns and active cards'). It implicitly distinguishes itself from prodpad_list_roadmaps and prodpad_get_product_roadmaps by being the single-item fetch by ID, but it never names those siblings 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 guidance on when to use this tool versus the sibling list/filter tools (prodpad_list_roadmaps, prodpad_get_product_roadmaps), nor any stated prerequisites such as needing a valid roadmap ID. Usage is only implied by the tool name and the single required parameter.

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