Skip to main content
Glama

Todo write

todo_write
Read-only

Maintain a structured todo list for the current task. Call this whenever a user request requires three or more distinct steps, when planning a complex multi-step task, or when tracking progress through a sequence. Set merge=true to update existing items by id and append new ones; set merge=false to replace the entire list. Status values: pending, in_progress, completed, cancelled. Mark items in_progress before starting them, completed immediately after finishing. Only one item should be in_progress at a time. The user sees this list rendered in the chat sidebar as a live checklist.

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

Input Schema

NameRequiredDescriptionDefault
mergeNoIf true, items in 'todos' are merged into the existing list by id (new ids appended). If false (default), the existing list is replaced.
todosYesOrdered list of todo items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior1/5

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

The description explicitly describes replacing the entire existing list, updating items by id, and mutating item statuses — an overwriting write operation. The annotations declare readOnlyHint=true, so the description directly contradicts the supplied safety signal and will mislead an agent about side effects.

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?

Front-loaded with purpose, then triggers, then semantics, then invariants — a sensible order with no filler. It is on the long side and repeats status values and merge behavior that the schema already documents.

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?

Covers purpose, trigger conditions, merge behavior, valid statuses, sequencing rules, and the fact that the user sees the list rendered live in the sidebar — a useful piece of context absent from the structured fields. It does not say what happens on unknown ids or whether the whole list is returned, but with no output schema that omission is minor.

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

Parameters4/5

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

Schema coverage is already 100%, so baseline is 3; the description adds real meaning by explaining the merge=true vs merge=false semantics in operational terms and by imposing the invariant that only one item may be in_progress at a time, which the schema does not encode.

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?

"Maintain a structured todo list for the current task" states a specific verb and resource, and the follow-on sentences make clear it is a planning/progress-tracking tool rather than a task executor. Nothing among the siblings overlaps, so an agent can identify it immediately.

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

Usage Guidelines5/5

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

Gives explicit activation conditions ("whenever a user request requires three or more distinct steps, when planning a complex multi-step task, or when tracking progress"), which is precisely the when-to-use guidance most tools lack. It also supplies operational sequencing rules: mark in_progress before starting and completed right after finishing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.