Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Fix Umlauts

cc_fix_umlauts
Idempotent

Repairs broken German umlauts in source code files by detecting 70+ corruption patterns and replacing them with correct characters, with optional dry-run preview and backup.

Instructions

Repairs broken German umlauts in source code files.

Args:

  • path (string): Path to the file

  • dry_run (boolean): Preview only

  • create_backup (boolean): Create backup

Detects 70+ patterns of broken umlauts and replaces them correctly.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file
dry_runNoPreview only
create_backupNoCreate backup

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.8

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare mutation (readOnlyHint=false), idempotence, and non-destructiveness. The description adds useful context: it repairs 70+ patterns, supports dry_run preview, and can create backups, which goes beyond the annotations without contradicting them.

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 and the description is short. The Args section duplicates schema information, which is slightly redundant, but overall it remains efficient and easy to scan.

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

Completeness4/5

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

For a file-mutating tool with no output schema, the description covers the core operation, pattern scope, dry-run preview, and backup behavior. It does not describe return values or error behavior, but annotations and schema cover the essential safety profile.

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 the schema already documents all three parameters. The description repeats the same parameter meanings ('Path to the file', 'Preview only', 'Create backup') without adding syntax, constraints, or behavioral detail beyond the schema.

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: 'Repairs broken German umlauts in source code files.' It is clear what the tool does, though it does not explicitly differentiate itself from sibling tools like cc_fix_encoding.

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 implied by 'in source code files' and the mention of 70+ broken umlaut patterns, but there is no explicit guidance on when to use this tool versus alternatives such as cc_fix_encoding or cc_cleanup_file.

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