3D Visualizer

Overview Schema Source Related Servers Discussions Admin

select_3d_region

Select point-cloud regions by object, scalar field, bounding box, or plane, then isolate and preview the highlighted subset. Clear restores full visibility.

Instructions

One-step select/isolate/focus with PNG preview. Select all points in an object, or intersect scalar field values, world box [minX,minY,minZ,maxX,maxY,maxZ], and plane halfspace ax+by+cz+d>=0. Creates a reversible highlighted point subset; clear restores prior visibility. Label IDs are numeric, not semantic object names: inspect attributes/pick first. No automatic segmentation; point clouds only. Replaces the previous selection. Disable highlight to preserve original colors. Moving the plane requires another select call.

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": "select_3d_region"
  }
}

Input Schema

Name	Required	Default
`field`	No
`focus`	No
`plane`	No
`action`	No	select
`bounds`	No
`detail`	No	summary
`values`	No
`isolate`	No
`preview`	No
`scene_id`	Yes
`highlight`	No
`object_index`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations are minimal (readOnlyHint=false, openWorldHint=false, destructiveHint=false) and the description does not contradict them. It adds substantial behavioral context: the selection is reversible, it replaces prior selections, it has a highlight option, and it does not perform automatic segmentation. This goes well beyond the annotations and fully discloses the tool's side effects and constraints.

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 description is a single dense paragraph of about 90 words. It front-loads the primary purpose, then adds behavioral notes. While it could benefit from bullet points for readability, every sentence contributes information and there is no fluff. It is concise given the tool's complexity (12 parameters) and well-structured logically.

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?

The description is largely complete for an agent to use the tool correctly. It covers the selection criteria, reversibility, replacement behavior, point-cloud constraint, label ID caveat, and preview/highlight options. It lacks explicit detail on the return format (though 'PNG preview' is mentioned) and does not enumerate all parameters, but given the absence of an output schema and the tool's complexity, it provides sufficient context to avoid misinvocation.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate. It explains key parameter semantics: bounds corresponds to the world box, plane to the halfspace, values to scalar field intersections, and object_index to the object. It also mentions highlight (disable to preserve colors) and action (clear restores visibility). While not every parameter (e.g., detail, focus, isolate) is individually described, the core selection modes and critical options are covered, providing meaningful value beyond the schema.

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?

The description clearly states the tool's purpose: to select/isolate/focus points in a 3D scene with one step, offering multiple selection criteria (object, scalar field, world box, plane halfspace). It distinguishes itself from sibling tools like manage_3d_selections by emphasizing the 'one-step' and 'replaces previous selection' nature, making it obvious when to use it.

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 description provides explicit usage guidance: it explains that selection is reversible ('clear restores prior visibility'), warns that label IDs are numeric (not semantic), notes the point-cloud-only limitation, and clarifies that it replaces the previous selection. While it doesn't explicitly name alternatives, it implies usage through phrases like 'one-step' and contrasts with more complex selection management, giving clear context for when to use it.

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