Planning System MCP Server

release_task

Release a claimed task without changing its status. Use for explicit handoff or abandonment of tasks.

Instructions

Release a claimed task without changing status. Use for explicit handoff or abandonment.

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

Input Schema

Name	Required	Description
`task_id`	Yes
`plan_id`	No	Auto-resolved from task if omitted
`message`	No	Optional log entry on release

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.8.1Apr 29, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries full burden. It clearly states the key behavioral trait 'without changing status', which is good. But it lacks details on prerequisites (e.g., task must be claimed), side effects (e.g., message logging), permissions, or reversibility.

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 two sentences, front-loads the purpose, and contains no redundant or irrelevant 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 no output schema, low parameter count, and adequate annotations from context signals, the description covers the core purpose and usage. However, it could be more complete by mentioning error conditions or what happens if the task is not claimed.

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 description coverage is 67% (2 of 3 params have descriptions). The description adds no additional parameter information beyond what the schema already provides. Per criteria, with coverage > 80% baseline is 3, but here coverage is 67%, still the description does not compensate.

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 uses a specific verb 'release' on a specific resource 'claimed task', and distinguishes from simply changing status by stating 'without changing status'. It also lists explicit use cases: explicit handoff or abandonment.

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

Usage Guidelines4/5

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

The description explicitly states when to use the tool ('for explicit handoff or abandonment'), giving clear context. However, it does not provide when-not-to-use guidance or name alternative sibling tools, though the purpose implies differentiation.

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