Skip to main content
Glama

task_plan

Idempotently create, update, or reorganize recursive task trees with dependencies, files, and target tests to keep multi-day project work structured across sessions.

Instructions

Idempotently create, update, or reorganize recursive tasks (task_id?, title, brief, files, target_tests, children) and depends_on edges ([upstream, downstream]).

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

Input Schema

NameRequiredDescriptionDefault
tasksYesRecursive list of task definitions.
depends_onNoArray of [upstream_id, downstream_id] dependency pairs.
project_idNoOptional project ID (auto-resolved when omitted).
parent_task_idNoOptional parent task ID to attach tasks beneath.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute one genuinely important trait: the operation is idempotent, so repeated calls are safe. It also implies create-vs-update branching via the optional task_id. It omits what happens to fields not supplied on an update, whether removal of children/dependencies is possible, how invalid dependency references are handled, and what the call returns.

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?

A single dense sentence that front-loads the verbs and the key behavioral word 'Idempotently' before the parameter enumeration. Every clause earns its place, though the parenthetical field list reads more like schema echo than added 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?

For a four-parameter tool with fully documented schema and no annotations, the description covers the operation's semantics, idempotency, and the recursive/dependency shape of the input, which is adequate for correct invocation. Since no output schema exists, the missing description of the return value (for example, generated task IDs needed to wire later depends_on pairs) leaves a real gap.

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 100%, so the baseline is 3. The description's field list and the '[upstream, downstream]' ordering restate what the schema already documents in its property descriptions, adding no format, constraint, or interaction semantics beyond it.

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 names specific verbs (create, update, reorganize) against a specific resource (recursive tasks) plus dependency edges, and enumerates the fields it touches. An agent knows exactly what domain this covers. It does not, however, distinguish itself from siblings such as task_update or ui_create_task, so a reader must infer the boundary from names alone.

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?

Usage is only implied: the phrase 'create, update, or reorganize' plus the 'task_id?' marker hints that omitting task_id creates while supplying it updates. There is no explicit when-to-use guidance, no statement of when to prefer this over task_update or the ui_* task tools, and no prerequisites spelled out.

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