Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Attach to a running CarMaker program

cm_standalone_attach

Attach to a running CarMaker simulation by process ID to configure a test run, start it, and store simulation quantities.

Instructions

Attach to a CarMaker simulation program that is already running, for example one started from a CarMaker Office window.

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": {
      "pid": "<pid>"
    },
    "name": "cm_standalone_attach"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidYesProcess id from cm_standalone_servers
speedNox real time; omit for CarMaker's maximum. Slower only if the user asks
startNoStart the run at once (needs testrun)
testrunNoTest run to configure (needed to start a run)
overridesNoTest-run keys to change in memory only, e.g. {'Vehicle': 'Car_B'} for another car. Vehicle keys (Body.mass) do not reach a standalone run: clone the vehicle
quantitiesNoQuantities to store
stop_after_sNoSafety stop at this simulation time in s

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.0
    • changedInput schema / properties / overrides / description
      Previous value: -"Test-run keys to change in memory only, e.g. {'Vehicle.DriverTemplate.FName': 'X'}"New value: +"Test-run keys to change in memory only, e.g. {'Vehicle': 'Car_B'} for another car. Vehicle keys (Body.mass) do not reach a standalone run: clone the vehicle"
    • removedInput schema / properties / realtime_factor
      Removed value: -{
-  "default": 1,
-  "description": "Speed relative to real time",
-  "exclusiveMinimum": 0,
-  "type": "number"
-}
    • addedInput schema / properties / speed
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "x real time; omit for CarMaker's maximum. Slower only if the user asks"
+}
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=false, and destructiveHint=false, so the safety profile is known. The description adds useful context that it targets an existing running program, but it does not explain control implications, multiple-attach behavior, or that optional start/testrun parameters can begin a run.

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?

The description is a single, front-loaded sentence with no wasted wording. It states the action and the key precondition immediately.

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 seven-parameter attach tool with rich schema descriptions and an output schema, the description establishes the core scenario. However, it omits that the same call can configure or start a test run and apply in-memory overrides, so an agent relying only on the description may underestimate the tool's scope.

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 seven parameters are already documented in the input schema, including pid, speed, start, testrun, overrides, quantities, and stop_after_s. The description adds no parameter-level detail, so the baseline of 3 applies.

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 gives a specific verb and resource: attach to an already-running CarMaker simulation program, with an example of an Office-started instance. The 'already running' condition implicitly distinguishes it from launch-style siblings, but it does not name the relevant alternatives.

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?

It clearly states the context for use: when a CarMaker simulation program is already running, such as one started from an Office window. It does not explicitly say when not to use it or name alternatives like cm_standalone_launch.

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