Skip to main content
Glama

scan_code_smells

Read-onlyIdempotent

Scan code for deferred work and shortcuts: TODO/FIXME comments, empty functions, hardcoded values, and debug artifacts. Surfaces technical debt for code quality audits and pre-release checks.

Instructions

Find deferred work and shortcuts: TODO/FIXME/HACK/XXX comments, empty functions & stubs, hardcoded values (IPs, URLs, credentials, magic numbers, feature flags), debug artifacts (console.log, debugger, var_dump, dd, binding.pry, pdb.set_trace, dbg!, printStackTrace, and 20+ other per-language debug markers). Surfaces technical debt that grep alone misses by combining comment scanning, symbol body analysis, and context-aware false-positive filtering. Use for code quality audit / pre-release checks. For performance-specific antipatterns use detect_antipatterns; for security issues use scan_security. Read-only. Returns JSON: { findings: [{ category, priority, file, line, message }], total, summary }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategories to scan (default: all)
scopeYesDirectory to scan (default: whole project)
priority_thresholdNoMinimum priority to report (default: low)
include_testsNoInclude test files in scan (default: false)
tagsNoFilter TODO comments by tag (e.g. ["FIXME","HACK"]). Only applies to todo_comment category
limitNoMax findings to return (default: 200)
Behavior5/5

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

Description explains behavioral traits beyond annotations: it uses comment scanning, symbol body analysis, and false-positive filtering, and states read-only. No contradiction with annotations.

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?

Description is well-structured and front-loaded with purpose. Slightly verbose but each sentence adds value; could be tightened slightly.

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

Completeness5/5

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

Despite no output schema, the description includes the exact return format. Covers purpose, usage, behavioral details, and output structure, making it complete for a complex tool with 6 parameters.

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 baseline is 3. Description provides high-level context but does not add significant meaning to individual parameters beyond what the schema already provides.

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?

Description clearly states the tool finds deferred work and shortcuts like TODOs, empty functions, hardcoded values, debug artifacts. It specifies the resources and actions, and distinguishes from sibling tools detect_antipatterns and scan_security.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'Use for code quality audit / pre-release checks.' Also gives alternatives: 'For performance-specific antipatterns use detect_antipatterns; for security issues use scan_security.'

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikolai-vysotskyi/trace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server