Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

run_observe

Read-only

Read a simulation's current state during execution, inspect results after failure, or retrieve a sample from a completed run using its job ID.

Instructions

Read the latest state while running or after failure, or a sample from a completed run.

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
sample_indexNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the temporal distinction between live, failed, and completed runs, which is genuine behavioral context. It does not say whether reads are blocking, whether a failed run returns partial data, or how large the returned state is.

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 filler, moving from live/failure reads to the completed-run sampling case. The phrasing is slightly compressed ('Read the latest state while running or after failure') but nothing is wasted.

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

Completeness2/5

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

With no output schema and no parameter descriptions, the description is the only source of semantics, yet it never describes what the observed state contains or what a 'sample' is. For a tool with an opaque return payload and two undocumented parameters, this leaves meaningful gaps an agent must guess at.

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%, so the description must carry parameter meaning, and it largely does not. 'A sample from a completed run' hints at sample_index but never explains that -1 (the default) means latest, and job_id's expected format or source is never mentioned. The compensation for the coverage gap is only partial.

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 pairs a specific verb (Read) with a specific resource (run state) and enumerates three retrieval modes: live state during execution, post-failure state, and a sample from a completed run. This lets an agent distinguish it from verification or cancellation siblings without opening the schema, though the term 'state' remains somewhat abstract.

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?

Usage is implied through the three scenarios (running, after failure, completed run), which is useful conditional context. However, no sibling is named as an alternative — an agent is not told when to prefer job_status or run_verify over this, and there are no exclusions or prerequisites stated.

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