Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

simulation_resume

Resume a paused simulation by job ID, then poll job_status to track progress and confirm it continues.

Instructions

Request resumption of a paused simulation; poll job_status.

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_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 disclose the important behavioral fact that resumption is asynchronous and requires polling job_status, which is genuinely useful context. It omits what happens if the job is not paused, whether the call is idempotent, or what a rejected request looks like.

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?

A single compact sentence with the action front-loaded and the follow-up step in a trailing clause. Nothing is wasted and nothing is buried.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, non-annotated tool with no output schema, the definition covers purpose, precondition, and the required next step. The remaining gap is the job_id contract and failure behavior, which is minor at this complexity level.

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?

The single job_id parameter has 0% schema description coverage, so the description must compensate. It implies job_id identifies the paused simulation's job via context but never states the expected format or provenance (e.g. returned by simulation_pause). This is only marginally better than the bare schema.

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 and resource ('Request resumption of a paused simulation'), which distinguishes it from simulation_pause and simulation_start by scope. It also names the related job_status tool, though it does not explicitly contrast itself with the other simulation lifecycle siblings.

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 a clear precondition ('paused simulation') and a clear follow-up action ('poll job_status'), so an agent knows when this applies and what to do next. It stops short of stating when not to use it, e.g. that a not-yet-started simulation should use simulation_start instead.

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