Skip to main content
Glama
carmaker-mcp
by dimitr-io

Export a result file

cm_results_export

Exports selected quantities from a CarMaker .erg result file at full resolution to MAT or CSV, with optional time-window filtering and safe non-overwriting output.

Instructions

Write quantities of a result file at full resolution (no thinning) to a MAT file (one double variable per quantity, dots as underscores, plus quantity_names and units) or a CSV file (header 'Time [s],Car.v [m/s],...': name and unit), in any folder of this computer. Never overwrites.

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": {
      "erg": "<erg>"
    },
    "name": "cm_results_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
ergYesResult file (.erg): absolute path, or relative to the project
fileNoTarget .mat or .csv (absolute, or relative to the result file's folder); default next to it
t_maxNoEnd of the time window in s
t_minNoStart of the time window in s
formatNoWhen file is not givenmat
quantitiesNoDefault: all

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

The 'Never overwrites' guarantee is genuine behavioral context that aligns with and enriches destructiveHint=false, and 'in any folder of this computer' clarifies filesystem scope. What remains undisclosed is what actually happens when the target exists (error vs. auto-rename) and whether a missing result file errors out.

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?

It is a single dense sentence that front-loads the action and format scope, with no filler. The nested parentheticals about MAT variable naming make it heavier to parse than strictly necessary, but every clause carries information.

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?

With an output schema present, return values need no explanation, and the description covers the write behavior, output formats and no-thinning semantics. Only the edge-case behaviors (existing target file, invalid path, empty quantity selection) 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 coverage is 100%, so the schema already carries parameter meaning and the baseline is 3. The description's added detail concerns output layout (variable naming, quantity_names/units, CSV header) rather than clarifying t_min/t_max or quantities semantics, which the description does not enrich.

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 specific verb and resource ('Write quantities of a result file ... to a MAT file or a CSV file') and pins down the exact output artifacts. It does not name or contrast with siblings such as cm_results_read or cm_results_plot, so the agent gets scope but no explicit discrimination.

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 output formats and 'full resolution (no thinning)' hint at when this tool is the right choice, but there is no statement of preconditions or of what alternative to use for read/plot/list operations. Usage is implied rather than stated.

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