Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_get

Read-only

Retrieve the current scene specification by scene ID to inspect or edit the active simulation scene.

Instructions

Get the current scene specification.

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": {
      "scene_id": "<scene_id>"
    },
    "name": "scene_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_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 the safety profile is known. Beyond that the description adds almost nothing: it does not say what happens when scene_id does not exist, whether "current" means live versus last-saved state, or what the retrieved data 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no filler and the action front-loaded, so nothing is wasteful. The problem is under-specification rather than verbosity — the brevity sheds information the agent needs rather than trimming redundancy.

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?

There is no output schema, so the description should explain what a "scene specification" contains and in what form it is returned; it does neither. For a lookup tool with an undocumented identifier and an opaque return type, the definition omits information an agent needs to call it correctly.

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?

The single parameter scene_id has 0% schema description coverage, so the description carries the full burden of explaining it and does not — it never states whether scene_id is a name, UUID, or path, nor whether it must reference an existing scene. With low coverage and no compensating text, this falls below the baseline.

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 description pairs a verb ("Get") with a resource ("the current scene specification"), so the basic action is identifiable. However, "specification" is never defined, and nothing distinguishes this read from plausible siblings such as scene_observe or scene_open, leaving the agent to guess what uniquely comes back.

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 at all: no statement of which scenarios call for retrieving the spec versus observing, opening, or validating a scene. The agent must infer the choice from tool names alone, which the description does nothing to support.

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