Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

job_status

Check simulation job progress and optionally wait for completion, saving a compact receipt to a caller-specified unused path; timeouts keep the same job ID for another wait.

Instructions

Check a job; optionally wait machine-side and save a compact completion receipt. For wait_seconds>0, the caller must choose a new unused absolute receipt_path in their own output directory. A timeout preserves the same job_id; wait again with a new unused receipt path. Waiting grants no physical acceptance. Configure a client timeout longer than wait_seconds.

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": "job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
receipt_pathNo
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: waiting happens machine-side, receipt paths must be new and absolute, timeouts preserve the same job_id, waiting grants no physical acceptance, and client timeouts must exceed wait_seconds. It does not describe return values or job status codes, which leaves some behavioral gaps.

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?

The description is front-loaded with the core action and then gives necessary operational constraints in four tight sentences. It avoids filler, though a few phrases such as 'Waiting grants no physical acceptance' are terse enough to require interpretation.

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 three-parameter status tool with no annotations and no output schema, the description covers invocation and waiting behavior well. However, it does not explain what the job status response contains or what status values mean, leaving a meaningful gap for a status-checking tool.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate. It explains receipt_path constraints for wait_seconds>0, what happens to job_id after timeout, and the relationship between client timeout and wait_seconds; only deeper type/default constraints remain undocumented.

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 states a specific verb and resource: 'Check a job' with an optional machine-side wait and receipt saving. It is clear what the tool does, though it does not explicitly distinguish itself from sibling job_cancel or explain status semantics.

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?

It clearly explains when to use the waiting behavior, how to choose an unused absolute receipt_path, how timeouts behave, and the client timeout requirement. It lacks explicit when-not-to-use guidance or direct comparison with job_cancel, but operational usage is well covered.

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