Skip to main content
Glama

doer_toggle_todo_item

Toggle or set the completion state of a checklist item in a Markdown todo list by index, line number, or matching text.

Instructions

Toggle or mark a specific task checklist item (- [ ] / - [x]) in a todo list by 0-based index, line number, or matching text

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>"
    },
    "name": "doer_toggle_todo_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique identifier of the todo list containing the item
indexNo0-based index of the target task checklist item among all checklist items in the list
completeNoExplicit completion status (true = - [x], false = - [ ]). If omitted, toggles current state.
match_textNoSubstring of the task text to search and match (case-insensitive)
line_numberNo1-based line number of the task item in the markdown source
render_markdownNoWhether to return rendered HTML in the response

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?

With no annotations, the description carries the full burden; it does disclose the mutation target (markdown checkbox state) and that omitting 'complete' toggles rather than sets. It stays silent on important behavior: precedence when index, line_number and match_text conflict, what happens on zero or multiple text matches, and whether the call errors or no-ops.

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?

One compact sentence, front-loaded with the operation and the checkbox notation, with zero filler. Nothing would be lost by keeping it this size.

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?

For a six-parameter mutation tool with no annotations and no output schema, the definition covers the core action but omits selector precedence, failure behavior, and any hint about the response shape (e.g. how 'render_markdown' affects returns). It is adequate to attempt a call, not adequate to predict its edge-case outcomes.

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 every parameter including 'complete', 'match_text' and 'line_number' is already documented in the schema. The description only restates the three selectors at a higher level and adds no format, precedence, or conflict-resolution meaning beyond the structured fields.

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 a specific verb pair ('Toggle or mark') and a specific resource ('a specific task checklist item (- [ ] / - [x]) in a todo list'), and enumerates the three addressing schemes. That is enough to distinguish it from generic list mutators like doer_update_todo_list, though no sibling is named 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?

It lists the three ways to target an item (index, line number, matching text) but never says when to prefer one over another, nor when to reach for doer_update_todo_list or doer_get_todo_list instead. Usage is implied by the description's phrasing rather than stated as guidance.

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