productplan-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_roadmap_milestones

Read-only

Retrieve milestones and key dates from a roadmap. Use this to answer scheduling questions like 'What are the key dates?'

Instructions

Get milestones (key dates) on a roadmap.

USE WHEN: "What are the key dates?", "Show milestones" Returns array of milestones with ID, title, and date. FAILS WHEN: roadmap_id not found (use list_roadmaps).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`roadmap_id`	Yes	Roadmap ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	The ProductPlan payload (object or array) returned by the API, passed through verbatim
`summary`	Yes	Human-readable summary of the result (e.g. "Found 3 roadmaps")

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv6.0.0Sep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "The ProductPlan payload (object or array) returned by the API, passed through verbatim",
+      "type": "object"
+    },
+    "summary": {
+      "description": "Human-readable summary of the result (e.g. \"Found 3 roadmaps\")",
+      "type": "string"
+    }
+  },
+  "required": [
+    "summary",
+    "data"
+  ],
+  "type": "object"
+}

First observedv5.0.0Mar 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds value by disclosing the return shape (array of milestones with ID, title, date) and the failure condition when the roadmap_id is invalid. This goes beyond the annotations and helps an agent anticipate outcomes.

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?

The description is three concise segments: purpose, when to use, and failure handling. Everything is front-loaded and directly actionable, with no filler or redundant phrasing.

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

Completeness5/5

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

For a single-parameter, read-only tool with an output schema, the description covers the essential context: what it returns, when to use it, when it fails, and how to recover. No significant gaps remain.

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

Parameters4/5

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

The schema only says 'Roadmap ID', which is minimal. The description adds that the ID must correspond to an existing roadmap (otherwise it fails) and suggests using list_roadmaps to discover valid IDs. This gives practical meaning beyond the bare parameter label.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves milestones (key dates) on a roadmap, which is a specific verb and resource. It is distinct from siblings like get_roadmap and get_roadmap_bars because it focuses on milestones only, and there is no other get_milestone tool.

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

Usage Guidelines5/5

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

Explicit 'USE WHEN' conditions ('What are the key dates?', 'Show milestones') guide when to invoke this tool. The 'FAILS WHEN' section names the failure mode (roadmap_id not found) and directs to list_roadmaps as an alternative for finding a valid ID.

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

Deploy Server