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

ellmos-clatcher-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fix_json

Repair broken JSON files by stripping comments, fixing trailing commas, converting single quotes, and removing BOM/NUL characters. Supports dry-run mode for analysis without writing.

Instructions

Repair broken JSON: strip comments, fix trailing commas, convert single quotes, remove BOM/NUL. Supports dry_run mode.

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the JSON file
dry_runNotrue = analyze only, false = write repaired file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided; the description mentions dry_run mode behavior but does not disclose potential side effects like overwriting the original file or creating backups, which are important for a repair tool.

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?

The description is a single, front-loaded sentence that efficiently conveys the tool's action and key features with no redundant information.

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 no output schema, the description omits what the tool returns (e.g., success status, repaired content), leaving an information gap for the agent about the tool's output.

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 coverage is 100%, and the description only repeats the dry_run behavior without adding extra meaning about path requirements or expected file format beyond the schema.

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?

The description clearly states the tool's purpose: 'Repair broken JSON' and lists specific fixes (strip comments, fix trailing commas, convert single quotes, remove BOM/NUL), making it distinct from sibling tools like fix_encoding or cleanup_file.

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 implies when to use (for JSON files with syntax issues) but does not provide explicit guidance on when not to use or mention alternatives among siblings like fix_encoding or convert_format.

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