Skip to main content
Glama

convert_logistics

Convert logistics files between EDI X12, EDIFACT, JSON, CSV, GPX, and GeoJSON to prepare supply chain data for downstream systems.

Instructions

Convert supply chain formats: EDI X12→JSON/CSV, EDIFACT→JSON, GPX↔GeoJSON

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

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input logistics 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

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the actual supported conversion matrix, which is narrower than the union of enum values (e.g. EDIFACT only goes to JSON), but it says nothing about overwriting an existing outputPath, whether parent directories are created, size limits, or what happens on an unsupported pair. For a tool that writes files to disk, those omissions are notable.

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 dense sentence with the supported formats front-loaded and zero filler; the arrow notation conveys the directionality efficiently. Slightly cryptic if read without the schema, but well structured.

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 file-writing conversion tool with no annotations and no output schema, the definition covers the input side well but leaves the write side undefined: overwrite policy, error/exit behavior on bad pairs, and any return value remain unstated. Adequate to attempt a call, not adequate to predict its side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the 3 baseline is met by the schema alone. The description earns above baseline by constraining which inputFormat/outputFormat pairs are actually legal — information the enums do not convey, since the output enum lists csv/geojson/gpx while EDIFACT only supports JSON. It still says nothing about the path parameters.

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?

Names a specific verb (Convert) and a specific resource domain (supply chain formats), then enumerates the exact transformations: EDI X12→JSON/CSV, EDIFACT→JSON, GPX↔GeoJSON. That is far more informative than the tool name alone and lets an agent recognize the domain (logistics/GIS). It stops short of naming a sibling to defer to (e.g. convert_geoscience for GPX cases), so it is clear but not differentiated against alternatives.

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 listed format pairs — an agent must infer that this tool is for EDI/EDIFACT/GPX files and that other converts (3D, audio, image) belong elsewhere. There is no explicit when-to-use or when-not-to-use statement and no reference to get_supported_formats for validation.

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