Skip to main content
Glama

convert_dev_format

Convert developer config and schema files between TOML, JSON, INI, ENV, XML, JSONL, Protobuf, and GraphQL formats for tool compatibility.

Instructions

Convert developer config/schema formats: TOML↔JSON, INI↔JSON, ENV↔JSON, XML→JSON, JSONL↔JSON, Protobuf schema→JSON, GraphQL schema→JSON

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_dev_format"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input config/schema file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden. It does add real behavioral information the schema lacks: the arrow notation reveals which conversion directions exist, since the inputFormat and outputFormat enums alone would permit unsupported combinations like JSON→XML. It says nothing about overwriting existing output files, directory creation, filesystem access requirements, or behavior on an unsupported pair.

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 no filler, and the compact arrow notation packs a lot of constraint into little space. It is telegraphic enough that a reader must already know why some pairs are one-directional.

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?

There is no output schema and no annotations, so the description is the only source of behavioral detail for a filesystem-write tool with two required absolute paths. Format support is complete, but overwrite semantics, error behavior, and output shape are left unaddressed.

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 all four parameters including auto-detection of inputFormat are already documented inline; baseline is 3. The description's only parameter-adjacent contribution is the implied pairing of formats, which is not stated in terms of inputPath/outputPath semantics.

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 names a concrete verb (convert) and resource (developer config/schema formats) and enumerates the exact supported format pairs, which clearly separates it from siblings like convert_document or convert_spreadsheet. It stops short of naming any sibling explicitly, so the differentiation is inferential rather than stated.

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 only implied by the format list; there is no explicit 'use this when' statement and no routing to alternatives such as get_supported_formats or batch_convert. The directional arrows (XML→JSON is one-way, TOML↔JSON is both ways) do communicate an important usage constraint, but the agent must infer that unsupported directions should be avoided.

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