Skip to main content
Glama
Sign In
API Hub MCP — 337+ Tools

API Hub MCP — 337+ Tools

by scotia1973-bot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

todo_finder

Scans source code to find TODO, FIXME, HACK, NOTE, and XXX comments. Identifies unfinished tasks and areas needing attention in your codebase.

Instructions

Find TODO, FIXME, HACK, NOTE, XXX comments in source code.

Parameters:
    code — Source code to scan for TODO/fixme comments.

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

Input Schema

NameRequiredDescriptionDefault
codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.4.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as case sensitivity, return format, or whether it scans the entire input. The minimal description leaves significant uncertainty about how the tool operates.

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?

The description is concise, with two sentences covering purpose and parameter. However, mixing parameter documentation into the main description instead of using the schema's description field makes it slightly less structured. Overall efficient.

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?

Given the tool's simplicity (one input string) and presence of an output schema, the description is minimally adequate. However, it does not explain behavior like scanning logic or edge cases, missing opportunities to fully inform the agent.

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?

The schema has 0% description coverage for the 'code' parameter, but the description adds a brief explanation ('Source code to scan for TODO/fixme comments'). This provides basic context beyond the schema's type-only definition, though it lacks details like character limits or encoding.

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 finds TODO, FIXME, HACK, NOTE, XXX comments in source code, providing a specific verb and resource. It distinguishes from sibling code analysis tools like code_stats or code_complexity by focusing on comment markers.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for scanning code comments but does not mention when to avoid it or compare with similar tools like search or analysis functions.

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