Skip to main content
Glama

Add steps to a task

plan

Add ordered steps to an open task, appending them after existing steps so an AI agent can structure work and track progress. Use read to review current steps first.

Instructions

Add steps to an open task, after those already there (read shows them). One done on its own is a part: propose with part_of.

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": "<task>",
      "steps": "<steps>"
    },
    "name": "plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesThe task id
stepsYesThe steps to add, in order, each at most 100 characters

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.43.2
    • changedInput schema / properties / steps / description
      Previous value: -"The steps to add, in order, one string each, at most 100 characters"New value: +"The steps to add, in order, each at most 100 characters"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that steps are appended after existing ones and that the task must be open. It also points to `read` for seeing current steps, which helps the agent reason about state. It does not describe what happens if the task is closed, but the annotations already cover safety and idempotency characteristics.

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 two short sentences and front-loads the core action. The second sentence is useful but phrased tersely enough that an agent may need to parse it carefully; still, there is no wasted wording.

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 simple two-parameter mutation tool with full schema coverage and annotations, the description provides the necessary context: open task, append behavior, and the `propose` alternative. It does not cover success or failure responses, but no output schema exists and the mutation is straightforward.

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 coverage is 100%, so the schema already explains both `task` and `steps`, including order and the 100-character limit. The description adds little parameter-specific detail beyond referencing `read` and the `part_of` alternative, so the baseline score for full schema coverage is appropriate.

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 states a specific verb and resource: 'Add steps to an open task.' It also specifies placement ('after those already there') and distinguishes the action from `propose` for standalone parts, so an agent can identify the operation without opening the schema.

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 makes clear this is for adding steps to an open task and names `propose` with `part_of` as the alternative when an item stands alone. It stops short of fully spelling out exclusions or prerequisites, but the key routing guidance is present.

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