Plane MCP

find_state

Look up a state by its case-insensitive name, optionally scoped to a project, and retrieve the matching state or return none.

Instructions

Find a state by (case-insensitive) name and return it, or None.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`project_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description must disclose behavioral traits itself. It does so by noting case-insensitive matching and returning None when no match is found. These are non-obvious behaviors that help the agent understand the tool's semantics. It does not mention potential errors or the role of project_id, but for a simple lookup, the key behaviors are covered.

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 of 13 words, front-loaded with the action and resource. Every word is necessary, and there is no redundancy or filler. It is a model of 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?

The tool is simple and the output schema exists, so return values are covered. The description addresses the primary lookup behavior and case-insensitivity. However, it omits the purpose or effect of 'project_id', which is a meaningful gap for a two-parameter tool. This prevents the description from being fully complete.

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

Parameters2/5

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

The schema has zero description coverage, so the description must compensate. It explains the 'name' parameter by indicating case-insensitive matching, but it says nothing about 'project_id', which is an optional parameter with unknown semantics. Since half of the parameters are undocumented both in the schema and description, the description only partially compensates for the coverage gap.

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 tool finds a state by name, uses case-insensitive matching, and returns it or None. This distinguishes it from sibling tools like list_states (which lists all states) and create_state/update_state (which modify states). The verb 'find' and resource 'state' are specific and unambiguous.

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 for retrieving a single state by name, but does not explicitly state when to use it over alternatives like list_states, nor does it mention exclusions or prerequisites. The guidance is implied rather than explicit, which meets the 'implied usage' benchmark but lacks clear when-to-use/when-not-to-use direction.

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