Skip to main content
Glama
olgasafonova

productplan-mcp-server

by olgasafonova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

get_launch_task

Read-only

Retrieve a specific launch task by launch ID and task ID to check its assignment, status, or details. Returns the task when both IDs are valid.

Instructions

Get a specific launch task by ID.

USE WHEN: "Show one specific task by ID", "Check task assignment or status" For all tasks, use get_launch_tasks. FAILS WHEN: launch_id or task_id not found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesTask ID
launch_idYesLaunch ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe ProductPlan payload (object or array) returned by the API, passed through verbatim
summaryYesHuman-readable summary of the result (e.g. "Found 3 roadmaps")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.0.0
    • 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"
+}
  2. First observedv5.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds a concrete failure mode (not found) beyond the structured data. While it doesn't discuss output or edge cases further, the safe read-only behavior is already covered; the description contributes the failure condition and the scoping distinction, which is sufficient for a simple getter.

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 compact and structured with labeled sections (USE WHEN, FAILS WHEN). The core purpose is front-loaded in the first sentence, and every sentence earns its place by either clarifying usage or warning about failure. No redundant content.

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 two-parameter getter with an output schema and readOnlyHint, the description covers purpose, usage, sibling routing, and failure conditions. Nothing an agent needs to invoke it correctly is missing—the output schema handles return details, and annotations handle safety profile.

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 parameters are already documented as 'Task ID' and 'Launch ID'. The description adds no additional semantics (e.g., relationship, format, or required combination). Given full schema coverage, the baseline of 3 is appropriate—the description doesn't need to compensate.

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 names the specific action ('Get') and resource ('launch task'), and explicitly differentiates from the sibling get_launch_tasks by saying 'For all tasks, use get_launch_tasks.' This leaves no ambiguity about which tool to select for a single task lookup.

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?

Provides explicit USE WHEN triggers (single task by ID, check assignment/status) and directly routes the agent to the sibling get_launch_tasks for all-tasks queries. The FAILS WHEN clause also sets expectations for error conditions, giving clear context on when not to rely on this tool.

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