Plane MCP Server

retrieve_role

Retrieve role details by ID, returning name, slug, and namespace for the specified role.

Instructions

Retrieve a role definition by ID.

Args: role_id: UUID of the role.

Returns: Role (name, slug, namespace).

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": {
      "role_id": "<role_id>"
    },
    "name": "retrieve_role"
  }
}

Input Schema

Name	Required	Description	Default
`role_id`	Yes

Output Schema

Name	Required	Description	Default
`name`	No
`slug`	No
`namespace`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.11Aug 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It discloses the return shape (Role with name, slug, namespace) but does not address error cases, permissions, or lack of side effects. This is adequate for a simple read operation but not richly transparent.

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 concise: one operative sentence followed by well-structured Args/Returns. No fluff, and it leads with the action.

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 simple retrieval tool with a single parameter and an output schema, the description is complete: it covers the purpose, the parameter, and the return shape. No additional context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains that role_id is a UUID of the role, adding meaning beyond the schema's bare string type. With only one parameter and 0% schema description coverage, this fully compensates for the missing schema details.

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 explicitly states 'Retrieve a role definition by ID,' providing a specific verb and resource. This clearly distinguishes it from list_roles and other retrieve tools by indicating that it fetches a single role by its identifier.

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?

The description gives no explicit guidance on when to use this tool versus list_roles or other alternatives. The only implied requirement is having a role_id, but no exclusions or alternative suggestions are provided.

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

Deploy Server