Skip to main content
Glama

simulation_control

Destructive

Run, pause, or stop an owned runtime simulation session via version-pinned Qt functions, then check native command state to confirm the action.

Instructions

Execute run, pause or stop using version-pinned Qt functions for an owned runtime session, then check native command state. A semantic project alone is insufficient.

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": {
      "action": "<action>"
    },
    "name": "simulation_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
projectNo
sessionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is known. The description adds workflow behavior beyond that: execution is version-pinned, it operates on an owned runtime session, and state should be re-checked afterwards. It still does not explain what the destructive aspect actually affects or what happens if the session is not owned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is front-loaded with the concrete actions and is efficient. The trailing sentence 'A semantic project alone is insufficient' is cryptic and jargon-heavy, costing more clarity than it buys.

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 destructive, non-read-only control tool with three poorly documented parameters and no output schema, the description covers the precondition and follow-up step but leaves the destructive semantics and result shape unspecified. It is adequate but with clear gaps an agent could stumble on.

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 0%, so the description must carry the load. It partially does: it clarifies that 'project' is a semantic project reference and that a session is an owned runtime session that must accompany it, and it echoes the three action values. It adds no format, identifier, or defaulting detail for the two string parameters.

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 names specific actions (run, pause, stop) applied to a simulation runtime session, and 'version-pinned Qt functions' plus 'owned runtime session' scope it away from the observe/stimulate/inspect siblings. It stops short of naming a specific alternative tool, so it is clear but not fully differentiating.

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

Usage Guidelines3/5

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

'Then check native command state' and 'a semantic project alone is insufficient' imply a required precondition (an owned runtime session) and a follow-up verification step, which is useful context. However, nothing explicitly states when to choose this over simulation_observe or simulation_stimulate, nor any when-not condition.

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