callimachus

Overview Schema Source Related Servers Discussions Admin

list_open_todos

Read-only

Find open TODOs left in past coding sessions, including task checkboxes and TODO/FIXME markers. Filter by text, project, or source to resume unfinished work.

Instructions

Open TODOs left in past sessions (task checkboxes, TODO/FIXME markers), newest first, filterable by text, project or source. Each has an id for complete_todo and the threadId it came from.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_open_todos"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max TODOs (default 20, max 100).
`query`	No	Case-insensitive text match on the TODO or its thread title.
`source`	No	Source filter (see search_threads).
`project`	No	Project path substring.

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": {
+        "todos": {
+          "items": {
+            "properties": {
+              "createdAt": {
+                "type": "integer"
+              },
+              "extractor": {
+                "type": "string"
+              },
+              "id": {
+                "type": "integer"
+              },
+              "originRef": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "projectPath": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "source": {
+                "type": "string"
+              },
+              "text": {
+                "type": "string"
+              },
+              "threadId": {
+                "type": "integer"
+              },
+              "title": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "required": [
+              "id",
+              "threadId",
+              "text",
+              "source",
+              "title",
+              "projectPath",
+              "createdAt",
+              "extractor",
+              "originRef"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "todos"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "notice": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "notice"
+      ],
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed6 schema fields changedv0.11.3Nov 6, 2026

removedInput schema / $schema

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

changedInput schema / properties / limit / description

Previous value: -"Max TODOs to return (default 100)."New value: +"Max TODOs (default 20, max 100)."

changedInput schema / properties / project / description

Previous value: -"Substring-match the project path (e.g. a repo path) to scope results."New value: +"Project path substring."

changedInput schema / properties / query / description

Previous value: -"Optional text search over the TODO text + thread title (case-insensitive)."New value: +"Case-insensitive text match on the TODO or its thread title."

changedInput schema / properties / source / description

Previous value: -"Optional source filter (see search_threads). Empty = all sources."New value: +"Source filter (see search_threads)."

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

Addedv0.6.0Jun 21, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are ordered newest first, the scope is limited to past sessions, and each row carries an id plus the originating threadId. It does not mention pagination/cursor behavior beyond the limit parameter.

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 compact sentences, front-loaded with the resource and scope before the filtering and id details. Every clause carries information; nothing is padded or redundant.

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?

An output schema exists, so return values need not be explained, and the definition covers inclusion criteria, ordering, filters, and the id/threadId linkage an agent needs to chain into complete_todo. Only minor details, such as how result volume is bounded in practice, are left implicit and are covered by the schema's limit.

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 baseline is 3: limit defaults, query matching semantics, source filter, and project substring are all documented in the schema. The description's 'filterable by text, project or source' largely restates those fields without adding syntax or matching details.

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 (list), a specific resource (open TODOs from past sessions), what counts as a TODO (task checkboxes, TODO/FIXME markers), and the ordering (newest first). It also names the sibling tool that consumes the ids, so an agent can distinguish it from complete_todo without opening either schema.

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?

The reference to 'id for complete_todo' implies a follow-up workflow, and the mention of filtering suggests when the filters apply. However, there is no explicit statement of when to use this versus a sibling such as search_threads or find_prior_work, and no exclusions or prerequisites, so the guidance remains implied.

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