Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Diff Files

cc_diff_files
Read-onlyIdempotent

Compare two files and display differences in unified diff format to inspect code changes and verify edits.

Instructions

Vergleicht zwei Dateien und zeigt Unterschiede im Unified-Diff-Format

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": {
      "file_a": "<file_a>",
      "file_b": "<file_b>"
    },
    "name": "cc_diff_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_aYesPath to first file
file_bYesPath to second file
context_linesNoNumber of context lines (default: 3)

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the output format (unified diff), which is genuine context, but says nothing about missing-file errors, binary files, or encoding handling.

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 front-loaded sentence with zero filler. It is efficient, though the extreme brevity leaves no room for the behavioural caveats a caller might need.

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 simple two-path comparison tool with no output schema, the description conveys purpose and return format, which is close to sufficient. It omits error behavior and edge cases (identical files, non-text input), and is written in German while the schema and sibling names are English, a minor inconsistency for an agent.

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 file_a, file_b and context_lines (with default 3, range 0-20) are fully documented in the schema. The description adds no parameter-level detail beyond that, which is the expected baseline.

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?

States a specific verb and resource ('Vergleicht zwei Dateien') plus the concrete output format ('Unified-Diff-Format'), which lets an agent understand exactly what it produces. It does not name a sibling or scope boundary, but no sibling tool offers diffing, so confusion risk is low.

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 explicit when-to-use guidance, no prerequisites (files must exist, text vs. binary), and no mention of alternatives or when not to use it. Usage is only implied by the verb 'compare two files'.

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