Skip to main content
Glama
Sign In
carmaker-mcp

carmaker-mcp

by dimitr-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Overwrite a quantity in a standalone run (DVA)

cm_standalone_dva_write

Overwrite a quantity in a running standalone simulation using Direct Variable Access. Set the absolute value and optionally choose the instance and override duration.

Instructions

Overwrite a quantity in a running standalone simulation (Direct Variable Access).

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "cm_standalone_dva_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesQuantity to overwrite
valueYesAbsolute value
instanceNoStandalone instance id such as 'sa1' (may be omitted while there is only one)
duration_msNoHow long the override lasts in ms (-1: until the run ends)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered. The description only adds that the target is a running standalone run and that the change is an overwrite; it does not disclose that the effect is time-bound (per duration_ms) or what happens when the run ends. With annotations carrying the safety bar, a 3 is appropriate.

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?

A single front-loaded sentence with no waste, stating the action and the target domain immediately. It is efficient, though the brevity is partly under-specification rather than true conciseness.

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?

An output schema exists so return values needn't be explained, and the schema fully documents the 4 parameters. However, for a state-mutating tool the description omits the relationship to cm_dva_write/cm_dva_release and the time-bounded nature of the override, leaving meaningful gaps for an agent choosing among the DVA siblings.

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 all four parameters are documented in the schema, including the duration_ms semantics ('-1: until the run ends'), so the baseline is 3. The description adds nothing about parameters beyond restating the overwrite action.

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 ('Overwrite') and resource ('a quantity in a running standalone simulation'), and expanding DVA signals the domain. It distinguishes itself from the plain cm_dva_write sibling only implicitly via 'standalone' in the title/name; the description never names the non-standalone alternative, so an agent must infer the split.

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

Usage Guidelines2/5

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

No when-to-use or when-not guidance. The counterpart cm_dva_release (which presumably removes the override) is never referenced, and the temporary nature of the write is not framed as usage guidance. The only context ('running simulation') is implied rather than stated as a precondition.

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