Skip to main content
Glama

Check off a todo

complete_todo
Idempotent

Check a todo off: it leaves the open list and shows under done. Works without a subscription.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe todo's id.

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 idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered by structured data. The description adds genuinely new context: the exact state transition (open list to done) and the fact that no subscription is required. It stops short of saying whether the change is reversible via reopen_todo.

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?

Two short sentences, front-loaded with the state transition and no redundant restatement of the name or title. Every clause contributes either the effect or a capability constraint.

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?

For a one-parameter, non-destructive, idempotent state-change tool with complete annotations and no output schema, the description covers effect and access requirement. Minor gaps remain: behavior when the todo is already done or the id is invalid.

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?

There is a single required parameter, fully documented in the schema as 'The todo's id.' with a minLength constraint. The description adds no format details, source of ids, or validation behavior, so the schema carries the burden and the baseline of 3 applies.

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 and resource ('Check a todo off') and adds the observable outcome ('it leaves the open list and shows under done'), so an agent knows exactly what state change occurs. It does not explicitly name the inverse sibling reopen_todo, so differentiation is implied rather than stated.

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 by the outcome description: call this when an open todo is finished. There is no explicit when-not guidance or pointer to reopen_todo for undoing the action, and the only extra constraint ('Works without a subscription') is a plan note rather than routing guidance.

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