minimal-mcp

complete_todo

Idempotent

Mark a specific todo as done using its ID. Get the ID from the todo list first, then set the task's status to completed.

Instructions

Mark a todo as done, by id.

Read todos://all first if you do not already know the id.

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": {
      "todo_id": "<todo_id>"
    },
    "name": "complete_todo"
  }
}

Input Schema

Name	Required	Description	Default
`todo_id`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`done`	Yes
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already convey idempotentHint=true and destructiveHint=false, so the description does not need to repeat those. It adds a useful instruction about reading todos://all for the id, but no new behavioral disclosure beyond what annotations already imply.

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 core action and immediately followed by the key usage hint. No filler or redundant content.

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 simple one-parameter tool with annotations and an output schema, the description fully covers what an agent needs to correctly invoke it. It states the action, the parameter, and the prerequisite for obtaining the id.

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?

The sole parameter todo_id is described by name and reinforced with 'by id' in the description. The schema provides integer type and required status, so the parameter is sufficiently clear even with 0% schema description coverage.

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?

The description uses a specific verb-object structure ('Mark a todo as done, by id') that clearly identifies the action and target resource. It naturally distinguishes itself from sibling tools add_todo and remove_todo.

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

Usage Guidelines4/5

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

The description provides an explicit prerequisite: read todos://all first if the id is unknown. It does not explicitly contrast with add/remove, but the guidance is clear and actionable.

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

Deploy Server