Retrieve current 3D scene details including object IDs, labels, positions, sizes, base heights, collisions, floor level, and room bounds to enable scene analysis and editing.
Return the current scene info: object ids, labels, world centers and sizes, base heights, collisions, floor_z, and room_bounds.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It states the operation is a read ('Return') and lists the returned data, which signals read-only behavior. However, it does not elaborate on potential side effects, permissions, or error conditions, though for a getter this is minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence that front-loads the verb and resource and then lists the returned fields. No filler words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters, an output schema exists, and the description enumerates the returned scene attributes, an agent can call this tool correctly without additional information. The description is sufficient for this simple read-only tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description cannot add parameter meaning. Baseline for 0 params is 4, and the description appropriately focuses on the output instead.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('Return') and resource ('current scene info') and enumerates the exact content fields (object ids, labels, world centers, etc.), making it distinct from sibling tools like render_scene or load_scene. No ambiguity about what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage – call this to retrieve current scene state – but does not explicitly state when to use it over alternatives or mention any exclusions. No reference to sibling tools or when this is preferred, leaving the agent to infer from the name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.