Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Validate JSON

cc_validate_json
Read-onlyIdempotent

Validates JSON files and returns detailed error information with exact error positions to help debug malformed JSON.

Instructions

Validates JSON with detailed error information and position.

Args:

  • path (string): Path to the JSON file

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

Input Schema

NameRequiredDescriptionDefault
pathYesPath to the JSON file

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description's contribution is that errors are reported with position details, which sets expectations for the diagnostic output; it says nothing about file-not-found handling or size limits.

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 first sentence is front-loaded and earns its place; the Args section is pure duplication of the schema description but costs only one line. No filler or hedging.

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?

A one-parameter read-only validator with no output schema needs little explanation, and the description does hint at the return content (error details plus position). The main residual gap is failure modes for unreadable or nonexistent files, which is minor for a tool this simple.

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 single parameter is documented in the schema as "Path to the JSON file"; the description's Args block just restates it verbatim. Baseline 3 applies because the schema carries the parameter semantics with no added constraint such as relative-vs-absolute paths.

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 ("Validates JSON") and adds a scope detail (detailed error information and position). It is distinguishable from the mutation sibling cc_fix_json, though it never names that alternative explicitly.

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 the verb: call this to check whether a JSON file is well-formed. There is no explicit when-to-use/when-not guidance and no pointer to cc_fix_json for the case where the agent wants to repair rather than report, so the agent must infer the boundary.

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