Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_validate

Read-only

Checks whether objects in a scene match supported schemas, helping catch unsupported types before simulation; does not perform physics validation.

Instructions

Check supported object schemas. This is not physics validation.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 scope context by ruling out physics validation, but says nothing about what a check actually returns (pass/fail, list of unsupported types), whether it fails on invalid schemas, or any limits – gaps that matter for a validation tool.

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?

Two short sentences with the exclusion up front and no filler; nothing is wasted. The brevity is appropriate in form, though it reflects under-specification rather than tight precision.

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 validation tool with an undocumented required parameter and no output schema to explain results, the description should state what gets checked and what the response represents. As written, an agent knows only that it is not physics validation, which is insufficient to call it 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?

There is one required parameter, scene_id, and schema description coverage is 0%, so the description carries the full burden of explaining it. Instead it adds nothing about the identifier's form, whether it must come from scene_open, or what happens with an unknown scene id.

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 gives a verb and resource ("Check supported object schemas"), but "supported object schemas" is ambiguous – it is unclear whether it validates schema declarations inside a scene, checks registry support for object types, or returns a compatibility report. The added negation ("This is not physics validation") differentiates it from a physics checker, which is useful, but no sibling tool is named and the core operation stays fuzzy.

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?

The only guidance is a negative exclusion ("not physics validation"), which steers agents away from one wrong assumption but never states when the tool should be used, what preconditions exist (e.g. an opened scene), or which sibling to choose for related checks. No alternatives are named, so the agent must infer usage from the scene_* catalog alone.

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