Skip to main content
Glama
goto-software

plane-mcp-server

retrieve_state

Retrieve a state's details using its ID and the project's UUID to manage project workflows.

Instructions

Retrieve a state by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID of the project
state_idYesUUID of the state

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
created_atNo
updated_atNo
deleted_atNo
nameYes
descriptionNo
colorYes
sequenceNo
groupNo
is_triageNo
defaultNo
external_sourceNo
external_idNo
created_byNo
updated_byNo
projectNo
workspaceNo

Implementation Reference

  • The `retrieve_state` function is the tool handler. It's decorated with @mcp.tool(), takes project_id and state_id as string params, calls client.states.retrieve(), and returns a State object.
    @mcp.tool()
    def retrieve_state(project_id: str, state_id: str) -> State:
        """
        Retrieve a state by ID.
    
        Args:
            project_id: UUID of the project
            state_id: UUID of the state
    
        Returns:
            State object
        """
        client, workspace_slug = get_plane_client_context()
        return client.states.retrieve(workspace_slug=workspace_slug, project_id=project_id, state_id=state_id)
  • Import of register_state_tools from plane_mcp.tools.states, which is called to register all state tools including retrieve_state.
    from plane_mcp.tools.states import register_state_tools
    from plane_mcp.tools.users import register_user_tools
    from plane_mcp.tools.work_item_activities import register_work_item_activity_tools
    from plane_mcp.tools.work_item_comments import register_work_item_comment_tools
  • register_state_tools(mcp) is called to register state tools with the MCP server, which includes retrieve_state.
    register_state_tools(mcp)
    register_workspace_tools(mcp)
    register_epic_tools(mcp)
    register_milestone_tools(mcp)
  • register_state_tools function that wraps all @mcp.tool() decorated functions including retrieve_state.
    def register_state_tools(mcp: FastMCP) -> None:
  • Test registration reference listing 'retrieve_state' as one of the state tools under test.
    "retrieve_state",
Behavior2/5

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

The description does not disclose behavioral traits beyond the basic read operation. No annotations are provided, so the description should convey idempotency, error handling, or permissions, but it does not.

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 concise sentence that immediately conveys the tool's purpose. No unnecessary words, and the structure is front-loaded.

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?

The tool has an output schema, so return values are documented elsewhere. However, the description lacks behavioral details such as idempotency or error responses. For a simple retrieval tool, it is minimally adequate but could be more 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?

Both parameters have descriptions in the input schema (100% coverage). The description does not add additional meaning beyond what the schema already provides, so baseline score of 3 applies.

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 ('Retrieve'), resource ('state'), and retrieval criterion ('by ID'). It distinguishes from sibling tools like 'list_states' which lists all states, and 'update_state' which modifies an existing state.

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 implies usage when a state ID is known, but it does not explicitly mention when not to use it or provide alternatives such as 'list_states'. The context is clear but lacks exclusions or alternative guidance.

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