Skip to main content
Glama

Find TODO Markers

find_todos
Read-onlyIdempotent

Scans source code for TODO, FIXME, and HACK markers to help you track unfinished work and technical debt.

Instructions

Find TODO, FIXME and HACK markers in a source tree.

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": {
      "code": "<code>"
    },
    "name": "find_todos"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code to search for TODOs
filePathNoFile path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered without the description. The description contributes the marker vocabulary (TODO/FIXME/HACK), which usefully bounds what counts as a hit. It does not disclose matching behavior (case sensitivity, whether strings/comments are distinguished) or the shape of results, which matters for a search tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the marker list is the most decision-relevant detail and appears immediately. It is arguably too terse for the questions it leaves open, but nothing in it is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only search tool with full schema coverage and annotations, the description is nearly sufficient. The gap is that it never says what comes back (match locations, counts, line numbers) and does not reconcile 'source tree' with the single-code-string input, which an agent must resolve before calling it correctly.

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 both parameters are already documented and the baseline of 3 applies. The phrase 'in a source tree' hints at path-based scoping but does not clarify how the required 'code' parameter relates to the optional 'filePath', which is the one genuine ambiguity an agent faces here. No format or syntax detail is added beyond the schema.

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?

States a specific verb ('Find') and a specific resource ('TODO, FIXME and HACK markers'), which is far more informative than the title alone. The scope phrase 'in a source tree' is slightly at odds with the schema's required single 'code' string plus optional 'filePath', leaving mild ambiguity about whether it scans a directory or a snippet. It is still clearly distinguishable from siblings like analyze_code or check_security.

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

Usage Guidelines2/5

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

The description gives no when-to-use or when-not-to-use guidance, and names no alternative among the many code-analysis siblings. An agent must infer from the marker list alone that this is a lightweight grep-style scan rather than a lint or analysis pass. No prerequisites or exclusions are stated.

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