Skip to main content
Glama
ellmos-ai

ellmos-codecommander-mcp

by ellmos-ai

Python Structural Edit

cc_python_structural_edit

Perform structural edits on Python files with preview, syntax check, and backup protection. Supports insert, delete, replace, and element-level operations.

Instructions

Prüft und wendet BACH-abgeleitete strukturelle Python-Edits mit Vorschau, Testdatei und Backup-Schutz an

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lineNo1-based line for position=line or replace_line
modeNopreview returns a diff, test writes a .test.py file, apply writes the sourcepreview
pathYesPython file to inspect or edit
contentNoInserted code or replacement line content
elementNoClass/function/method name, e.g. MyClass.method
elementsNoComma-separated element names for create_edit_file
positionNoInsert position for operation=insert
edit_fileNoEdit file path for merge_edit_file
operationYesStructural edit operation
class_nameNoTarget class for position=in_class
output_pathNoOptional output path for test or edit-file modes
python_pathNoPython executable path for syntax checks
syntax_checkNoCompile-check edited Python before writing
create_backupNoCreate a backup when mode=apply
indent_spacesNoIndent inserted non-empty lines
Behavior4/5

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

The description discloses key behaviors: it applies edits with preview, test file modes, and backup protection. Annotations provide no destructive hint, but the description clarifies the tool can modify files with safeguards. 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?

The description is a single sentence that captures the core functionality. It is concise and front-loaded with the key idea, though it could be slightly more structured.

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 15 parameters and no output schema, the description is relatively brief. While the schema covers parameter details, the description lacks guidance on how the different operations (inspect, insert, etc.) relate to each other or the overall workflow.

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% with all parameters having descriptions. The description does not add extra meaning beyond the schema, but the schema itself is thorough, so baseline 3 is elevated to 4.

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 clearly states it handles structural Python edits with preview, test file, and backup protection. The name also indicates Python structural editing. However, the phrase 'BACH-abgeleitete' is obscure and may not be understood by all agents.

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?

The description implicitly suggests use for structural edits but provides no explicit guidance on when to use this tool versus sibling tools like cc_generate_python_code or cc_analyze_methods. No when-not-to-use or alternative comparisons are given.

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/ellmos-ai/ellmos-codecommander-mcp'

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