Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Diagnose Imports

cc_diagnose_imports
Read-onlyIdempotent

Diagnose import problems in Python, JavaScript, or TypeScript files by detecting unused bindings, duplicates, risky relative imports, and import-order issues.

Instructions

Diagnoses import issues in Python, JavaScript, or TypeScript files.

Args:

  • path (string): Path to a .py, .js/.jsx/.mjs/.cjs, or .ts/.tsx/.mts/.cts file

Detects: Unused bindings, duplicates, relative-import risks, and import-order issues

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_diagnose_imports"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to a supported Python, JavaScript, or TypeScript file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / path / description
      Previous value: -"Path to the Python file"New value: +"Path to a supported Python, JavaScript, or TypeScript file"
  2. First observedv1.3.8

TDQS

A3.5/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 openWorldHint=false, so the safety profile is fully covered. The description adds genuine value by naming the four detection categories and the accepted file extensions, but it never says what a diagnosis returns (issue list? severities? line numbers?) or whether it offers fixes, which matters for a tool with no output schema.

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 purpose is front-loaded in the first sentence and the detection list is compact. The Args block restates the single schema parameter almost verbatim, which is minor waste, but overall there is little padding.

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 one-parameter, read-only, non-destructive tool with full annotation coverage this is close to sufficient, but two things are missing: no indication of the response shape (there is no output schema) and no routing guidance against cc_organize_imports, which an agent will likely want to call immediately after a diagnosis.

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% and there is a single required parameter, so the baseline is 3. The description's Args block goes beyond the schema by spelling out the exact accepted extensions (.py, .js/.jsx/.mjs/.cjs, .ts/.tsx/.mts/.cts), which the schema only calls "a supported Python, JavaScript, or TypeScript file" — a meaningful disambiguation for the agent.

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 states a specific verb and resource ("Diagnoses import issues") plus the supported language scope, and enumerates the defect classes it looks for (unused bindings, duplicates, relative-import risks, import-order issues). It does not differentiate itself from the closely related siblings cc_organize_imports and cc_runtime_import_diagnose, so an agent must guess which of the three to call.

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: point it at a supported file and it reports import problems. There is no explicit when-to-use, no prerequisites, and no statement of when to prefer cc_organize_imports (fixing/reordering) or cc_runtime_import_diagnose (runtime resolution), which is a real ambiguity given three import-related siblings.

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