Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Plot result files in IPGControl

cm_results_plot

Plots quantities from CarMaker .erg result files in IPGControl without MATLAB, overlaying up to eight runs and returning a plot image for analysis.

Instructions

Plot quantities of result files in IPGControl, IPG's plotting program; needs no MATLAB. The window stays open for the user (the next plot replaces it) and a picture comes back as an image. This server has no MATLAB evaluation: for MATLAB figures use a MATLAB server, or cm_results_export.

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": {
      "ergs": "<ergs>",
      "quantities": "<quantities>"
    },
    "name": "cm_results_plot"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoQuantity for the x axis (default: Time), e.g. 'Car.Distance'
ergsYesResult files (.erg), absolute or relative to the project; several are overlaid
pictureNoAlso return a picture of the plot
quantitiesYesQuantities to plot, e.g. ['Car.ay', 'Car.YawRate']

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real behavioral context beyond the annotations: the IPGControl window stays open for the user and the next plot replaces the previous one, and a picture is returned as an image. Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=false), so these GUI-side-effect disclosures are genuinely valuable. Still silent on timing/latency when opening a GUI window.

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

Conciseness5/5

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

Two compact sentences, front-loaded with the core action, then the window/image behavior, then the alternative routing. No filler and nothing repeated from the schema.

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?

For a read/side-effect-lite tool with four well-documented parameters and no output schema, the description covers what the tool does, its GUI side effect, and what comes back (an image). It leaves unclear whether any numeric/structured data is returned alongside the picture, which slightly limits completeness.

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% and each parameter already has a description with examples and defaults, so the baseline is 3. The description's only parameter-relevant addition is that a picture comes back as an image (clarifying the `picture` flag's effect); it adds nothing about `x`, `ergs` overlay behavior, or quantity limits beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — plot quantities of .erg result files inside IPGControl — and immediately scopes it (IPG's plotting program, no MATLAB required), which distinguishes it from cm_results_export and from MATLAB-server tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent away from this tool when MATLAB figures are wanted (use a MATLAB server or cm_results_export), giving a clear use/no-use split. It does not mention prerequisites such as the project or result files needing to be present/loaded first, so it stops just short of full when/when-not coverage.

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

Deploy Server

Other Tools