ProdPad MCP Server

Get ProdPad Key Result

prodpad_get_keyresult

Read-onlyIdempotent

Fetch a specific key result by ID from ProdPad, enabling quick access to OKR progress and details for review.

Instructions

Get a specific key result by ID.

Args:

id (string): Key result UUID

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_keyresult"
  }
}

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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds no behavioral context beyond that — no note about auth scope, not-found behavior, or what is returned.

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?

Two short, front-loaded lines with no padding. The Args block duplicates the schema's id description, a minor redundancy, but overall the text is tight.

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

Completeness3/5

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

For a single-parameter read tool whose annotations cover the safety profile, this is minimally adequate. No output schema exists and the description does not indicate the return shape, but the simplicity of the tool keeps the gap small.

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 the id parameter is already fully documented (including that it may be numeric or UUID), which the description's restatement adds nothing to. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (Get) and resource (key result) scoped by ID, which lets an agent separate it from the list_* siblings. However it does not explicitly distinguish itself from other get-style siblings like get_objective or get_product, so it falls short of a 5.

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 versus prodpad_list_keyresults, prodpad_get_objective_keyresults, or prodpad_get_product_keyresults. The verb 'get' combined with 'by ID' implies the fetch-one use case, but the description never states it or names alternatives.

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