Skip to main content
Glama

Find TODOs

find_todos
Read-only

Scan a project folder for TODO, FIXME, and HACK comments, returning file, line, and comment text so you can locate and triage pending code tasks.

Instructions

Scan a project folder for TODO, FIXME and HACK comments. Returns file, line and comment text.

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

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the project folder
tagsNoWhich tags to look for (default: all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the return shape (file, line, comment text), which is genuinely useful with no output schema, but leaves out key behavior: whether the scan is recursive, how large trees or binary files are handled, and result limits.

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?

Two short sentences, front-loaded with the action and followed by the return value; no filler. Slightly terse on scope, but nothing is wasted.

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 two-parameter read-only tool, this covers action, filters and output fields. The remaining gap is scan scope (recursion, ignored directories), which matters for correctness expectations but is not essential to invoke it.

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%, so both parameters are documented in the schema, including the tag enum and the 'default: all' note. The description's mention of TODO/FIXME/HACK restates rather than extends the schema, so the baseline 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?

States a specific verb and resource ("Scan a project folder for TODO, FIXME and HACK comments") plus the return shape (file, line, comment text). It is clear enough to distinguish from a stats/aggregation sibling, though it never names todo_stats explicitly.

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 only implied by "Scan a project folder" — an agent can infer this is the raw listing tool and todo_stats the aggregate, but the description gives no explicit when-to-use or when-not-to-use guidance and no prerequisites (e.g., whether the path must exist).

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

Deploy Server

Other Tools