Skip to main content
Glama
Sign In
io.github.neogeweb3/code-health-suite

io.github.neogeweb3/code-health-suite

by neogeweb3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

scan_todos

Scan source code for TODO, FIXME, and other technical debt markers, returning file, line, severity, and message. Optionally enrich with git blame metadata.

Instructions

Scan source code for technical debt markers: TODO, FIXME, HACK, XXX, BUG, NOTE, OPTIMIZE, REFACTOR comments. Returns items with file, line, tag, severity, and message. Optionally enriches with git blame metadata.

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

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by specific tag (e.g., TODO, FIXME, HACK).
pathYesFile or directory path to scan.
blameNoEnrich with git blame metadata (author, date). Slower.
severityNoFilter by minimum severity level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It correctly implies a read-only operation and mentions the optional git blame enrichment, but it does not explicitly state side effects, performance characteristics (beyond the 'slower' note in the schema), or any limitations. This is adequate but not exhaustive.

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?

The description is two sentences, tightly packed with relevant details. It lists the tags, describes the output, and mentions the optional enrichment without any filler.

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?

While there is no output schema and no annotations, the description covers the return structure and the main functionality. It lacks some contextual detail like sorting or pagination, but for a scan tool it is sufficiently complete for an agent to understand what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description adds value by enumerating the detectable tags and describing the return fields (file, line, tag, severity, message), which goes beyond the schema's basic parameter descriptions.

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?

The description clearly states the tool scans for specific technical debt markers and returns structured details. It distinguishes itself from sibling tools like get_todo_score by focusing on raw scan results rather than aggregated scores.

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 does not provide explicit guidance on when to use this tool versus alternatives such as get_todo_score. While the purpose implies raw scanning, there is no statement about when to prefer it for detailed inspection or when to use scoring tools instead.

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