Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

plan_update

Update a step's status and add optional notes in an existing project plan to track progress, mark blockers, and keep work aligned.

Instructions

Update step status and notes in an existing project plan.

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": {
      "step": "<step>",
      "status": "<status>"
    },
    "name": "plan_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional progress note
stepYes1-based step number
statusYestodo, doing, done or blocked

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is carried by structured data. The description adds only that status and notes are the mutated fields; it does not say whether note replaces or appends, whether an invalid step number errors, or whether updates are idempotent.

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?

A single front-loaded sentence naming the mutation and its scope, with no filler. Every clause earns its place and nothing is buried.

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?

With no output schema, 100% schema coverage, and no annotations gap, the definition is workable but thin for a mutation tool: it does not state what happens to the plan when a step moves to 'blocked', whether notes accumulate, or what a successful update returns.

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 schema already documents the 1-based step number, the four allowed statuses, and the optional note. The description merely echoes those fields and adds no format, validation, or edge-case detail beyond what is structured.

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 gives a specific verb and resource: 'Update step status and notes in an existing project plan.' That distinguishes it from plan_create (new plans) and plan_get (reads) by naming the mutation target and the 'existing' precondition, though it never names those siblings explicitly.

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 implied rather than stated: 'in an existing project plan' signals the precondition that a plan must already exist, and 'step' implies step targeting. There is no explicit when/when-not guidance and no pointer to alternatives such as plan_create for initial plan construction.

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