Skip to main content
Glama

Edit a todo

edit_todo
DestructiveIdempotent

Change a todo's title, body or star. Only the fields sent change. A new body replaces the whole body.

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": "edit_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe todo's id.
bodyNoReplaces the whole body (Markdown).
titleNoThe new title, one short line.
importantNoStarred todos sort first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it clarifies that omitted fields are preserved and that body updates are whole-value replacements, which is the key destructive nuance an agent must know before editing.

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?

Three short sentences, front-loaded with the action and scope, then the partial-update rule, then the body-replacement caveat. Every sentence carries distinct information with no filler.

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?

With annotations covering safety and no output schema needed, the description supplies what an agent needs to call it correctly: required id, optional fields, and non-clobbering semantics. It would be fully complete if it either reconciled "star" with the "important" parameter or noted how title/body validation failures are surfaced.

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 all four parameters, and the description adds little beyond restating them. The one substantive addition, that a sent body fully replaces the existing one, is useful but also present in the schema's "Replaces the whole body (Markdown)." Note that the description calls the field "star" while the schema names it "important," a minor naming mismatch that could slow field mapping.

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?

"Change a todo's title, body or star" names a specific verb and resource and enumerates the mutable fields, so an agent can distinguish it from add_todo or complete_todo. It stops short of explicitly naming a sibling to disambiguate against, which keeps it at 4 rather than 5.

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?

"Only the fields sent change" and "A new body replaces the whole body" give solid partial-update semantics that would otherwise be guessed. There is no explicit when-to-use versus when-not-to-use guidance, e.g. no pointer that status changes belong to complete_todo/reopen_todo rather than this tool.

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.

Resources