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

Open IPGMovie

cm_movie_open

Open CarMaker's IPGMovie 3D animation window before a run to record it, or take over an open one; restart it to fix internal picture errors.

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.

Input Schema

TableJSON 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

TableJSON 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.3/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, not open-world). The description adds genuinely non-obvious behavior: the window only records a run while open, and it can take over an already-open instance. Minor gaps remain (idempotency of repeat calls, what state it returns), but this is meaningful context beyond annotations.

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 tight sentences, front-loaded with the action and the critical timing constraint, with 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. The description covers purpose, the required pre-run timing, and the downstream consumer (cm_movie_snapshot), which is everything 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 description coverage is 100% and the sole 'restart' parameter is fully documented in the schema, so the baseline is 3. The phrase 'take over one that is open' loosely hints at the restart/idempotency model but adds no syntax or value detail beyond the schema.

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 (Open) and resource (IPGMovie, CarMaker's 3D animation window), and clarifies the 'take over an existing instance' case. It also names the sibling it feeds (cm_movie_snapshot), so an agent can distinguish it from the other cm_* tools.

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 explicit timing guidance: 'Open it BEFORE a run: it records a run only while it is open', which is the key usage condition. It does not state when NOT to open it or list alternatives for the same goal, so it falls just short of a 5.

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