Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Check Python Indentation

cc_check_indentation
Read-onlyIdempotent

Detects missing colons, unindented return/yield lines, and mixed tabs/spaces in Python files or directories to catch indentation errors before runtime.

Instructions

Prüft Python-Dateien auf fehlende Doppelpunkte, unindentierte return/yield-Zeilen und gemischte Tab-/Leerzeichen-Einrückung

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

Input Schema

NameRequiredDescriptionDefault
pathYesPython file or directory to check
recursiveNoRecurse into subdirectories when path is a directory
max_issuesNoMaximum number of issues to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.3.16

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds valuable detail by enumerating exactly which indentation defects are reported, but it never states that results are reported rather than fixed, nor how the capped issue list is shaped.

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?

A single compact sentence that front-loads the resource and then lists the detected defects in a scannable series. No filler, though it is so terse that scoping information is omitted entirely rather than trimmed.

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?

For a read-only checker with three fully documented parameters and no output schema, the description covers what is checked but not what comes back (a list of issues with file/line locations, truncated at max_issues). That return-shape gap is the main missing piece.

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%, with path, recursive, and max_issues each documented in the schema, so baseline is 3. The description adds no parameter-level meaning such as whether recursive applies only to directories or how max_issues truncation is signalled.

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?

The description names a specific verb (prüft = checks) and resource (Python-Dateien) and enumerates the exact defect classes detected: missing colons, unindented return/yield, mixed tabs/spaces. That distinguishes it reasonably well from the broader cc_analyze_code sibling, though it does not explicitly name that sibling.

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?

There is no guidance on when to use this versus cc_analyze_code or cc_python_structural_edit, and no statement of prerequisites or exclusions. The agent must infer from the sibling list that this is the narrow indentation-specific check.

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