Skip to main content
Glama

TODO stats

todo_stats
Read-only

Counts TODO, FIXME, and HACK comments per file and ranks them by frequency so you can see which files carry the most outstanding work.

Instructions

Count TODO/FIXME/HACK comments per file, sorted by most first.

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": "todo_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the project folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the aggregation and sort order of the result. It does not disclose scan scope (recursive? respects ignore rules?), whether counts are per-marker or combined, or the output shape beyond ordering.

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?

A single compact sentence with zero filler; the resource and the ordering constraint are both front-loaded.

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, read-only tool with no output schema, the description conveys the aggregation and sort order, which is most of what an agent needs. Remaining gaps are recursion scope and the exact return structure, which are relatively minor.

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% and the single path parameter is documented in the schema as an absolute project folder path. The description adds no further meaning about the path or its scope, so the baseline of 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 (count) and a precise resource (TODO/FIXME/HACK comments) and even describes the resulting ordering. It does not distinguish itself from the sibling find_todos, so an agent must infer that this tool aggregates/counts while the sibling presumably lists.

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: an agent can guess this is for aggregate counts rather than line-by-line listings, aided by the 'per file, sorted by most first' phrasing. There is no explicit when-to-use, when-not-to-use, or reference to the find_todos alternative.

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