Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_open

Creates or reopens a scene specification using a scene ID so agents can initialize or resume simulation scenes for editing and validation.

Instructions

Create or reopen a 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_open"
  }
}

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?

With no annotations, the description carries the full burden and does not meet it. It never says whether this is a read-only lookup or a state-creating mutation, whether it is idempotent, what happens if scene_id already exists versus does not, or what the caller gets back. "Reopen" hints at stateful session semantics that are left completely unexplained.

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, which is structurally fine. The brevity is under-specification rather than efficiency, though, so it earns only a middling score.

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?

For a tool with no annotations and no output schema, the definition should describe the mutation/session semantics and the return value (a scene handle? a status?), and it does neither. The single required parameter is also left undefined, so an agent cannot call this confidently.

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 coverage is 0%, so the description must compensate for the single parameter and does not. The critical ambiguity is whether scene_id is an identifier of an existing scene to reopen or a new name the caller is assigning; that distinction determines the correct call but is never addressed.

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?

"Create or reopen a scene specification" gives a verb pair and a resource, so the general intent is recoverable. But "create or reopen" fuses two distinct outcomes without saying which applies when, and nothing distinguishes it from siblings like scene_get or scene_apply. An agent knows roughly what domain it is in, not exactly what the call does.

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 guidance on when to call this versus scene_get (read an existing scene) or scene_apply, and no prerequisites or exclusions are stated. The agent must infer the routing decision entirely from sibling names, which the definition does not reference.

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