callimachus

by BetaBots-LLC

Overview Schema Source Related Servers Discussions Admin

Rust

Local

complete_todo

Idempotent

Mark a TODO as done using its id from list_open_todos so it leaves open lists and stays completed across re-indexing.

Instructions

Mark a TODO done (by its id from list_open_todos) so it drops out of the open lists. Persists across re-indexing.

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

Name	Required	Description	Default
`id`	Yes	The TODO's `id` from list_open_todos.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.11.4Nov 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "done": {
+          "type": "boolean"
+        },
+        "id": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "id",
+        "done"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.11.3Nov 6, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / id / description

Previous value: -"The TODO's id (the `id` field from list_open_todos)."New value: +"The TODO's `id` from list_open_todos."

removedInput schema / title
```
Removed value: -"CompleteTodoArgs"
```

Addedv0.6.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world behavior. The description adds two pieces of real context beyond them: the observable effect (the item leaves the open lists) and durability ('persists across re-indexing'). It still says nothing about failure modes or reversibility, so it is useful but not rich.

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 action and effect, with no redundant wording. Nothing could be removed without losing information.

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 mutation with an output schema and full annotation coverage, the description supplies what an agent needs to call it correctly. Only minor gaps remain, such as behavior when the id is invalid or the TODO is already completed.

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 coverage is 100% and the single id parameter is fully documented in the schema, including its origin. The description only restates that provenance ('by its id from list_open_todos'), adding no format or edge-case detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Mark a TODO done') plus the effect ('drops out of the open lists'), and names where the id comes from. An agent can distinguish this from siblings like list_open_todos or record_gotcha without opening any schema.

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?

Implies the usage context clearly: call it with an id obtained from list_open_todos when a TODO is finished. It does not spell out exclusions (e.g. what to do if the TODO is already done, or that there is no undo), so it stops short of explicit when-not guidance.

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