Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Convert Format

cc_convert_format
Idempotent

Converts files between JSON, CSV, INI, YAML, TOML, XML, and TOON formats using explicit source and target paths, enabling structured data transformation for different tools and workflows.

Instructions

Converts between JSON, CSV, INI, YAML, TOML, XML, and TOON formats.

Args:

  • input_path (string): Source file

  • output_path (string): Target file

  • input_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon"

  • output_format (string): "json" | "csv" | "ini" | "yaml" | "toml" | "xml" | "toon"

  • json_indent (number): JSON indentation

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": {
      "input_path": "<input_path>",
      "output_path": "<output_path>",
      "input_format": "<input_format>",
      "output_format": "<output_format>"
    },
    "name": "cc_convert_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_pathYesSource file
json_indentNoJSON indentation
output_pathYesTarget file
input_formatYesInput format
output_formatYesOutput format

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

C2.9/5.0
Behavior2/5

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

Annotations already disclose that the tool writes, is idempotent, is non-destructive, and is not open-world. The description adds no behavioral detail beyond annotations, such as whether output_path is overwritten or what happens on conversion failure.

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

Conciseness3/5

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

The purpose sentence is front-loaded and clear, and the overall description is not bloated. However, the Args section duplicates schema descriptions and does not add meaningful new 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?

For a simple file-conversion tool, the required parameters and format options are fully described by the schema. Gaps remain around return behavior, error handling, and overwrite semantics, especially since no output schema is present.

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 parameters and enums. The description merely repeats the schema argument descriptions without adding format-specific semantics or edge-case guidance.

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: converting between a clear list of file formats. It is distinguishable from most code-analysis siblings, though it does not explicitly differentiate itself from other conversion tools such as cc_md_to_html or cc_md_to_pdf.

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?

The description implies that it is used for format conversion, but it provides no explicit guidance on when to use it versus alternatives. It also omits prerequisites such as whether paths must exist or whether target files are overwritten.

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