Skip to main content
Glama

doer_append_to_todo_list

Append task items or Markdown sections to a specified todo list, automatically formatting entries as unchecked checklist items.

Instructions

Append one or more task items or markdown sections to a todo list (items are automatically formatted as '- [ ] ...')

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": {
      "id": "<id>",
      "items": "<items>"
    },
    "name": "doer_append_to_todo_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list to append items or sections to
itemsYesList of task checklist items or markdown lines to append (automatically normalized to - [ ] format)
section_headerNoOptional markdown header under which to append items (e.g., '## Next Up' or 'Bugs')
render_markdownNoWhether to return rendered HTML in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully establishes additive, non-destructive semantics ('Append', not overwrite) and the automatic '- [ ] ...' normalization, but says nothing about error behavior for a bad id, permissions, or what the response contains.

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 front-loaded sentence with the core action stated first and the formatting behavior in a parenthetical. No filler or repetition, though the parenthetical largely duplicates the schema's wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter tool with complete schema coverage and no output schema, the description covers the action, the payload type, and the auto-formatting side effect. The remaining unknowns (errors, response shape) are modest and partially covered by the render_markdown parameter.

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 all four parameters are already documented in structured form, which sets the baseline at 3. The description reinforces the items parameter and gestures at sections, but adds no syntax or format meaning beyond the schema's own normalization note.

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 ('Append') and resource ('a todo list') plus the payload ('one or more task items or markdown sections'), which is enough to distinguish it from get/list/delete siblings. It stops short of explicitly contrasting with doer_update_todo_list, so it is clear but not fully sibling-differentiated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement of when to append versus updating or recreating a list, and no prerequisites (e.g., that the target list id must already exist). The agent must infer call conditions from the name alone.

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