Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Open IPGMovie

cm_movie_open

Opens or takes over CarMaker's IPGMovie 3D animation window before a run so it records the simulation for later snapshot viewing; set restart to reset a failing movie.

Instructions

Open IPGMovie, CarMaker's 3D animation window (or take over one that is open). Open it BEFORE a run: it records a run only while it is open, and cm_movie_snapshot can then show any moment of it. Needs the MATLAB session; without it use cm_standalone_launch(movie=true).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cm_movie_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
restartNoClose a running IPGMovie and start it anew: the way out when its pictures fail with an internal error. It then holds no run

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • addedInput schema / properties / restart
      Added value: +{
+  "default": false,
+  "description": "Close a running IPGMovie and start it anew: the way out when its pictures fail with an internal error. It then holds no run",
+  "type": "boolean"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare it is not read-only and not destructive; the description adds real context beyond that: it only records while open, it requires the MATLAB session, and it can take over an existing window. It does not detail what happens to an in-progress recording on take-over, keeping it just short of a 5.

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?

Three tight sentences, front-loaded with the core action, then the timing constraint, then the prerequisite/alternative. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 the prerequisites, timing constraint, and fallback path an agent needs to invoke it correctly.

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% and the single 'restart' parameter is fully documented in the schema, including its error-recovery purpose. The description adds no parameter detail beyond that, so the baseline 3 applies.

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 ('Open IPGMovie, CarMaker's 3D animation window') and clarifies the take-over case. It also names the related siblings (cm_movie_snapshot, cm_standalone_launch) so the agent can place it in the workflow.

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

Usage Guidelines5/5

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

Explicitly says to open it BEFORE a run and why ('it records a run only while it is open'), and names the alternative when no MATLAB session exists: cm_standalone_launch(movie=true). Both the when and the fallback are stated.

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