Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Runtime Import Diagnose

cc_runtime_import_diagnose
Read-only

Diagnose Python runtime import failures by executing modules in isolated subprocesses with configurable timeouts, helping identify project import errors and dependency issues.

Instructions

Führt BACH-abgeleitete Python-Runtime-Importdiagnosen in isolierten Subprozessen aus

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

Input Schema

NameRequiredDescriptionDefault
pathYesPython project directory or file
modulesNoOptional module list: package.mod:Class,other.module
max_modulesNoMaximum auto-discovered modules to import
python_pathNoPython executable path; defaults to PYTHON/PYTHON_EXECUTABLE/python
timeout_secondsNoTimeout per isolated import subprocess

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

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false. The description adds genuine context beyond that by saying execution happens in "isolierten Subprozessen", which explains the isolation model. However, it does not disclose that importing project modules can execute arbitrary top-level code, nor does it mention timeout enforcement or failure behavior — relevant given the timeout_seconds param and the fact that readOnlyHint=true is debatable for a subprocess-running tool.

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 dense sentence with no filler; the resource and execution model are front-loaded. It is slightly under-specified for its length and leans on an undefined term ("BACH-abgeleitet") that occupies space without informing the agent.

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

Completeness2/5

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

A 5-parameter tool with no output schema, whose whole value is the diagnostic result, leaves the agent with no idea what a successful response contains (per-module status? errors? imports resolved?). Given it spawns subprocesses with configurable timeouts and paths, the omission of return shape and failure semantics is a substantive gap, and the absence of sibling differentiation compounds it.

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 every parameter (path, modules, max_modules, python_path, timeout_seconds) is already self-documented with defaults, bounds and format hints. The description adds no semantics about what "diagnosis" of those modules yields or what the modules syntax means, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb ("Führt ... aus" / executes) and resource ("Python-Runtime-Importdiagnosen in isolierten Subprozessen") are identifiable, so the core action is graspable. But the qualifier "BACH-abgeleitet" is unexplained jargon, and there are two closely named siblings (cc_diagnose_imports, cc_organize_imports) that the description does nothing to distinguish from. Purpose is legible but not disambiguated.

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 statement of when to use this tool versus cc_diagnose_imports, cc_organize_imports, or cc_analyze_code, and no prerequisites or exclusions. The agent must infer selection purely from the name. No guidance is provided beyond the one-line purpose.

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