Skip to main content
Glama
MD MCP Plugin

MD MCP Plugin

by yanling37

world_adapter_inspect_3d

Inspect the current 3D viewport, Qt mapping, gizmo state, fixed Grid Properties action, and candidate method signatures to diagnose scene alignment and unit mismatches.

Instructions

Read the current 3D viewport, Qt mapping, gizmo state, fixed Grid Properties action and candidate method signatures. Qt scene units are not world mm.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "world_adapter_inspect_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_msNo
scene_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. "Read" does signal a non-mutating operation, and "Qt scene units are not world mm" is a genuinely valuable disclosure that prevents misinterpreting returned coordinates. However, it says nothing about cost/latency, whether state is captured atomically, or what the response contains, so it is only partially transparent.

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 enumerated payload front-loaded and the unit caveat appended where it is most likely to be read before interpreting results. Minimal waste, though the noun list could be tightened.

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 pure inspection call with no output schema and no annotations, the description does enumerate the surfaces being inspected, which is the core of what it needs to convey. It falls short on both parameters and on the shape of the returned data, so an agent still cannot call it confidently without opening the schema.

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 description coverage is 0%, so both budget_ms and scene_token are entirely undocumented in structured data. The description never mentions either parameter, leaving the agent to guess what scene_token scopes or how the default 750 ms budget affects the call.

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?

"Read the current 3D viewport, Qt mapping, gizmo state..." gives a concrete verb and an enumerable set of resources, and the 3D framing implicitly separates it from the sibling scene_adapter_inspect_2d. The trailing item "candidate method signatures" is opaque and drags the definition slightly toward a grab-bag, but an agent can still tell what class of tool this is.

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 statement of when to call this versus the many neighboring inspect tools (world_gizmo_scale_inspect, world_grid_step_inspect, world_adapter_read_camera), nor any precondition or exclusion. The unit caveat is a reading caveat, not usage guidance.

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

Deploy Server

Other Tools