Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_observe

Read-only

Retrieve a live or last camera preview, or a completed camera image, for a specified simulation job and camera.

Instructions

Return a live/last preview (when enabled) or a completed camera image.

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>",
      "camera": "<camera>"
    },
    "name": "scene_observe"
  }
}

Input Schema

NameRequiredDescriptionDefault
cameraYes
job_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds a genuine nuance, that a preview may or may not exist depending on enablement and may fall back to a completed image, but it leaves open what happens when neither exists (error vs empty), whether the call blocks until an image is ready, and what form the image arrives in.

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?

It is a single front-loaded sentence with no filler, but that brevity comes at the cost of substance rather than being earned economy. The parenthetical '(when enabled)' interrupts the core clause without resolving the ambiguity it raises.

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, no annotation detail on the return path, and 0% schema coverage, the description should explain what the caller receives (path, URL, base64, metadata) and how preview vs completed image are distinguished. It does none of that, leaving an agent unable to act on the result.

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 two required parameters, so the description carries the full burden and largely fails: 'camera' is only obliquely echoed in 'camera image', and job_id is never mentioned, nor is any relationship between job and camera validated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Return' plus the resource 'preview ... or completed camera image' tells the agent this fetches a visual artifact, but terms like 'live/last preview' and 'completed camera image' are undefined and the distinction from sibling run_observe is never made. An agent can guess the general purpose but not the precise outcome.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives such as run_observe, which plausibly overlaps. The only conditional hint, '(when enabled)', describes a system state rather than a tool-selection rule, so the agent must infer the context entirely.

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