3D Visualizer

Overview Schema Source Related Servers Discussions Admin

pick_3d_point

Read-only

Pick a point in a 3D scene using normalized canvas coordinates without moving the camera. Retrieve world XYZ, hit/miss status, and point attributes for inspection.

Instructions

Pick normalized canvas XY without moving the camera. Returns hit/miss, world XYZ, object and decoded point indices and scalar attributes. Mesh/splat picks may have null indices; never infer object identity from those.

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>",
      "screen": "<screen>"
    },
    "name": "pick_3d_point"
  }
}

Input Schema

Name	Required	Default
`detail`	No	summary
`screen`	Yes
`scene_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds independent value with the mesh/splat null-index caveat and the explicit assurance about not moving the camera. It also discloses the return payload, which sets accurate expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no filler. The core action and the most critical caveat are front-loaded, and every clause contributes useful information.

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

Completeness4/5

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

For a read-only pick tool with an output schema, a defaulted enum, and simple required params, the description covers the essential usage conditions and the important null-indices warning. The only minor gap is not explicitly explaining the 'detail' parameter, but the enum and the existence of an output schema mitigate the risk.

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. It does for the 'screen' parameter by explaining 'normalized canvas XY,' which matches the 0..1 range constraints, but it does not explain 'scene_id' or clarify how 'detail' affects the output. The return-payload sentence hints at output content but does not connect it to the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Pick'), resource ('normalized canvas XY'), and the key behavior ('without moving the camera'), which distinguishes it from camera navigation and capture siblings. It also names the return fields, so an agent knows exactly 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.

Usage Guidelines4/5

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

The 'without moving the camera' phrasing gives clear context that this is a read-only picking operation rather than a navigation/capture tool. It does not explicitly name an alternative or provide when-not-to-use guidance, but the context is sufficient for selection among the sibling tools.

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