Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_module

Get a module's details by its module ID within a specified project.

Instructions

Retrieve a module by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
module_idYesUUID of the module

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
total_issuesNo
cancelled_issuesNo
completed_issuesNo
started_issuesNo
unstarted_issuesNo
backlog_issuesNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
description_textNo
description_htmlNo
start_dateNo
target_dateNo
statusNo
view_propsNo
sort_orderNo
external_sourceNo
external_idNo
archived_atNo
logo_propsNo
created_byNo
updated_byNo
projectNo
workspaceNo
leadNo
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the action itself. It fails to state that this is a read-only operation or describe the output, which is critical for transparency.

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 extremely concise at 5 words, which is efficient for a simple retrieval tool. However, it could include a brief mention of the output without sacrificing conciseness.

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?

Given that an output schema exists and schema coverage is complete, the description is mostly adequate for a simple retrieval. However, it lacks context about the return value or read-only nature, which would make it more complete for an agent.

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?

The input schema covers 100% of parameter descriptions, so the baseline is 3. The description adds no additional meaning beyond what the schema provides.

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 'Retrieve a module by ID' clearly states the verb (retrieve) and resource (module), which distinguishes it from sibling tools like list_modules or create_module. However, it could be more specific by mentioning the required IDs.

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 provides no guidance on when to use this tool versus alternatives such as list_modules or other retrieve_* tools. No when-to-use or when-not-to-use information is given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/goto-software/plane-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server