Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

simulation_pause

Requests a cooperative pause of a running simulation timeline and provides job_status polling to confirm acknowledgment.

Instructions

Request a cooperative timeline pause; poll job_status for acknowledgment.

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": {
      "job_id": "<job_id>"
    },
    "name": "simulation_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does add real value by calling the pause "cooperative" (i.e., a request, not a guaranteed halt) and flagging that acknowledgment comes via job_status. It omits whether in-flight work is preserved, whether the pause is reversible, permission requirements, and whether the call blocks.

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?

One tight sentence with the action front-loaded and the follow-up step second; nothing is wasted. It is arguably over-compressed given the missing parameter and behavior detail, but structurally it is clean.

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 one-parameter control tool with no annotations and no output schema, the description covers the essential async workflow (request, then poll job_status), which is the main thing an agent needs. It remains incomplete on the meaning of job_id and on the semantics of a "cooperative" pause that may not take effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must compensate and does not: it never explains what job_id identifies (the simulation job being paused) or whether it is the pause request's own ID versus the target job's ID. The reference to job_status only vaguely hints at the linkage.

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 action ("Request a cooperative timeline pause") on an identifiable resource, and names the sibling job_status as the follow-up. The only ambiguity is what "timeline" refers to (simulation run vs. global), but the tool name and required job_id make the intent recoverable.

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 concrete post-call guidance: poll job_status for acknowledgment, which tells the agent this is asynchronous and must be followed up rather than assumed complete. It does not state when not to use it or contrast with siblings like simulation_resume or job_cancel, so it falls 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.