productplan-mcp-server

Overview Schema Source Related Servers Discussions Admin

get_objective

Read-only

Retrieve objective details and key results by providing an objective ID. Use to check OKR progress, with valid IDs obtained from list_objectives.

Instructions

Get objective details with key results.

USE WHEN: "Tell me about objective X", "OKR progress" FAILS WHEN: objective_id not found (get valid IDs from list_objectives).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`objective_id`	Yes	Objective ID from list_objectives

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

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the failure behavior when objective_id is not found, which is useful. However, it does not disclose other behaviors such as response structure or potential pagination, but given annotations, the added failure info earns a 3.

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 concise with a front-loaded purpose statement followed by clearly labeled USE WHEN and FAILS WHEN sections. Every line adds value without redundancy, making it easy to scan.

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?

For a single-parameter read-only tool with an output schema (indicated), the description covers the purpose, usage triggers, failure mode, and ID sourcing. It doesn't explain return format, but the output schema handles that, so the description is adequately complete.

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% with 'Objective ID from list_objectives' in the parameter description. The tool description essentially repeats this in the FAILS WHEN note, adding no new semantics beyond the schema. Baseline of 3 applies since the schema fully documents the parameter.

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 clearly states the tool retrieves objective details including key results, which specifies the verb and resource. It differentiates from sibling tools like get_key_result by mentioning 'objective details with key results', making its scope clear even without listing every sibling.

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

Usage Guidelines4/5

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

Provides explicit USE WHEN examples ('Tell me about objective X', 'OKR progress') and a FAILS WHEN condition for invalid objective_id, pointing to list_objectives for valid IDs. This gives clear usage context and a fallback source, though it doesn't explicitly exclude alternative tools like get_key_result.

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

Deploy Server