Skip to main content
Glama
Sign In
ellmos-clatcher-mcp

ellmos-clatcher-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fix_umlauts

Repair corrupted German umlauts caused by encoding mismatches. Analyzes or fixes files with double-encoding or cp1252 errors.

Instructions

Fix broken German umlauts from double-encoding or cp1252 artifacts (ä→ä, ö→ö, etc.)

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": "fix_umlauts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the file
dry_runNotrue = analyze only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided. Description does not disclose whether the tool modifies the file in-place, requires backup, or other behavioral traits. The dry_run parameter hints at analysis, but effects of actual fix are unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence efficiently conveys purpose and examples with no redundancy.

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?

Given simple tool with two well-described params and no output schema, description covers essential purpose. Could mention return values or confirmation of changes, but adequate for straightforward task.

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 covers 100% of parameters with descriptions. The description adds clarifying examples for the fix operation, but does not add meaning beyond what schema already provides for each parameter.

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

Purpose5/5

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

Description clearly states the tool fixes broken German umlauts from double-encoding or cp1252, with specific character examples (ä→ä, etc.). It distinguishes itself from sibling 'fix_encoding' by being specific to umlauts.

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?

No explicit guidance on when to use this tool vs alternatives like 'fix_encoding'. The context of German umlauts is implied, but no when-not-to-use or comparison provided.

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

Deploy Server

Other Tools