productive-mcp-rb2

get_person

get_person

Read-onlyIdempotent

Retrieve detailed information about a specific person using their Productive ID. Get name, role, and other details from Productive.io.

Instructions

Get detailed information about a specific person by their Productive ID.

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": {
      "person_id": "<person_id>"
    },
    "name": "get_person"
  }
}

Input Schema

Name	Required	Description	Default
`person_id`	Yes	The ID of the person to retrieve (required)

Output Schema

Name	Required	Description	Default
`id`	Yes
`firstName`	Yes
`lastName`	Yes
`email`	No
`title`	No
`role`	No
`status`	Yes
`companyId`	No
`createdAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0-alpha.7May 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe, idempotent behavior. The description adds minimal context by saying 'detailed information' but does not disclose additional behavioral traits like error handling or rate limits.

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 a single sentence with no wasted words. It is front-loaded with the core purpose and efficiently communicates the essential information.

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?

Given the tool's simplicity (one parameter, no nested objects, output schema exists), the description adequately covers the purpose. It could mention that an output schema is available, but the information is complete for an agent to invoke the tool correctly.

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 coverage is 100%, and the description adds no extra meaning beyond the schema's parameter description. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 action (Get detailed information), the resource (person), and the identifier method (by their Productive ID). It distinguishes the tool from list_people by specifying a single person retrieval.

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

Usage Guidelines3/5

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

The description implicitly suggests using the Productive ID but does not provide explicit when-to-use guidance or alternatives. It lacks directives on when to choose this over list_people or other similar tools.

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

Deploy Server