Skip to main content
Glama
SimScene MCP Server

SimScene MCP Server

by ros-claw

scene_measure

Read-only

Measures authored render bounds and bottom anchors for selected scene objects, optionally reporting AABB overlap candidates to review layout interference; does not certify physical clearance.

Instructions

Measure authored world render bounds and bottom anchors, including imported units/axes/variants and rigid visual attachments. Optional include_overlap_candidates returns AABB intersections among selected objects to review initial layout interference; empty compound space and deliberate contact can be false positives. It does not certify physical clearance. Imported outer bbox is not a support surface.

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>",
      "ids": "<ids>"
    },
    "name": "scene_measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
scene_idYes
include_overlap_candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint=false already supplied, the description adds genuine behavioral context: overlap detection is AABB-based and prone to false positives, results are not a physical-clearance certification, and an imported outer bbox is not a support surface. These are non-obvious interpretation caveats an agent cannot infer from annotations or schema.

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?

The core purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct caveat rather than restating the name. It is terse and fragmentary in places ("Imported outer bbox is not a support surface"), but nothing is wasted.

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

Completeness3/5

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

For a read-only measurement tool with no output schema, the description should say more about what is returned (structure, units, per-object grouping). It covers the overlap flag's output conceptually but leaves the primary measurement results underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 compensate, and it only meaningfully explains one of three parameters (include_overlap_candidates). The semantics of ids (which kind of object identifiers, required array) and scene_id, plus the units/format of the measurements, are left unstated.

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?

"Measure authored world render bounds and bottom anchors" gives a specific verb and resource, with scope qualifiers (imported units/axes/variants, rigid visual attachments). It is clearly a read-only measurement tool, distinguishable from planning/validation siblings, but no sibling is named to sharpen the contrast.

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

Usage Guidelines4/5

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

It states when the optional include_overlap_candidates flag is useful (reviewing initial layout interference) and when its output should be distrusted (empty compound space, deliberate contact are false positives). The caveat that it "does not certify physical clearance" is real exclusion guidance, though no explicit alternative tool is recommended for clearance checks.

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