productplan-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_launch_section

Read-only

Retrieve a specific checklist section by providing its launch ID and section ID. Use this tool to fetch one section's details when you know the exact identifiers.

Instructions

Get a specific checklist section by ID.

USE WHEN: "Show one specific checklist section by ID" For all sections, use get_launch_sections. FAILS WHEN: launch_id or section_id not found.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`launch_id`	Yes	Launch ID
`section_id`	Yes	Section 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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safe read behavior is covered. The description adds a useful behavioral detail beyond annotations: the tool fails when launch_id or section_id is not found. This is meaningful context for error handling.

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 description is short and well-structured with USE WHEN and FAILS WHEN sections. The quoted use case is slightly redundant with the opening sentence, but the sibling routing and failure disclosure earn their place.

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?

With a 100% documented schema, an output schema, readOnlyHint annotation, and explicit sibling differentiation, nothing essential is missing. The agent knows what the tool does, when to use it, when it fails, and where to route for the plural case.

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 launch_id and section_id are already documented in the schema. The description only repeats the 'by ID' concept and the failure condition; it does not add new parameter-level meaning.

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 uses a specific verb and resource: 'Get a specific checklist section by ID.' It also explicitly distinguishes this tool from the sibling get_launch_sections, making its scope unambiguous.

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?

It provides an explicit USE WHEN condition, names the alternative for fetching all sections (get_launch_sections), and gives a FAILS WHEN condition. An agent can confidently decide between this and its sibling without extra inference.

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

Deploy Server