Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Edit a project data file

cm_edit
Destructive

Change keys in IPG CarMaker project files in place with backup, logging, and only edited lines altered. Requires idle simulation; reload test run afterward.

Instructions

Change keys in a project file in place (backed up first, logged; only the edited lines change). Requires an idle simulation; load the test run again afterwards. Driver parameters belong in the driver template (kind 'driver', 'Template/'), which other test runs share: say which changed.

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": {
      "kind": "<kind>",
      "name": "<name>",
      "overrides": "<overrides>"
    },
    "name": "cm_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesKind of project data; selects the folder below <project>/Data
nameYesFile name relative to the kind's folder
overridesYesKeys to set, e.g. {'Road.FName': 'SKIDPAD.rd5'}; a null value removes the key

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: the mutation is 'backed up first, logged', and only the edited lines change, which materially softens the destructiveHint=true signal. It also discloses the idle-simulation prerequisite and the required follow-up reload of the test run — behavioral facts an agent cannot get from the schema or annotations.

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?

Front-loads the core action and its safety behavior in one tight sentence, then adds only the driver-template caveat. Dense but every clause earns its place; slightly telegraphic phrasing costs it a point.

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?

An output schema exists so return values need not be explained, and the description covers preconditions, backup/logging behavior, and the shared-driver-template edge case. Complete for a 3-param mutation tool, with only the missing explicit sibling contrast as a gap.

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 baseline is 3; the description adds real value by clarifying that driver overrides belong in the driver template (kind 'driver', 'Template/<name>') and that the affected test runs should be identified. That nuance is not present in the schema.

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?

States a specific verb and resource ('Change keys in a project file in place') and clarifies the scope ('only the edited lines change'). It is distinguishable from cm_create/cm_read, but never explicitly names a sibling or contrasts against cm_model_set, so an agent must infer the boundary itself.

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?

Gives clear preconditions ('Requires an idle simulation; load the test run again afterwards') and an exclusion about where driver parameters belong. It stops short of naming an alternative tool for other edit paths, but the context for invoking it is solid.

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