3D Visualizer

Overview Schema Source Related Servers Discussions Admin

export_3d_selection

Export the active or named 3D subset to a new binary PLY file, preserving RGB, normals, and scalar attributes. Returns the file path without overwriting existing files.

Instructions

Write the active or named subset to a NEW binary .ply under configured roots (maximum 256 MiB). Preserve decoded RGB, normals, scalar attributes, decoded indices, and original source_row when available (depth raster: pixel_v*width+pixel_u). Coordinates are object-local; header stores local_to_world and source origin. Returns a path, never point data/base64. No overwrite; not a lossless copy of the original file's numeric types.

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>",
      "path": "<path>"
    },
    "name": "export_3d_selection"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`path`	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.5/5.0

Behavior5/5

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

Annotations only provide readOnlyHint=false and destructiveHint=false, so the description carries the burden and does it well. It discloses the 256 MiB cap, attribute preservation, object-local coordinates, header transform storage, return-type behavior, no-overwrite guarantee, and non-lossless numeric fidelity—all beyond what annotations convey.

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?

Three dense sentences with no filler. The first sentence delivers the core action and primary constraint, while subsequent sentences add preservation details, coordinate behavior, return format, and caveats. Every sentence earns its place.

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

Completeness5/5

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

Given the tool's complexity and sparse annotations, the description is notably complete: it covers operation, size limit, preserved attributes, coordinate frames, header contents, return shape, overwrite behavior, and fidelity caveat. Since an output schema exists, return-value structure need not be repeated. The only small gap is scene_id/path semantics, which does not undermine overall completeness.

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 for missing parameter documentation. It does clarify that 'name' refers to a named subset and that output goes under configured roots, but it never explains the required scene_id parameter or the expected path format. This partial compensation is adequate but not complete.

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 states a specific verb and resource ('Write the active or named subset to a NEW binary .ply') and clearly distinguishes this from sibling tools like open_3d_files, capture_3d_view, or select_3d_region. The unique export-to-file purpose is unmistakable.

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 makes the intended usage clear: export a selected 3D subset to a new .ply file, subject to size and overwrite constraints. It does not explicitly name alternatives or say when not to use it, but no sibling tool performs this export operation, so the context is sufficient.

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