3D Visualizer

Overview Schema Source Related Servers Score Discussions Admin

transform_3d_object

Move, rotate, scale, or reset 3D objects in a scene without altering source files or camera. Supports local/world transforms, pivots, quaternions, matrices, and undo.

Instructions

Transform one cloud/mesh without changing source files or camera. Translate/scale use vector XYZ; rotate uses vector axis plus angle degrees (90 for quarter turns); quaternion uses XYZW, normalized. Matrix is affine 4x4 COLUMN-MAJOR, matching inspection (transpose row-major UI input). Default composes currentdelta in local space; world uses deltacurrent. pivot=center rotates/scales around the current bounding-box center; explicit XYZ pivot uses the chosen space; omitted pivot is the coordinate origin. Undo restores the last of up to 50 agent edits per object. replace=True sets an absolute transform. Invert/reset act on the current matrix. Inspect local_to_world to verify. Visibility, point size and coloring use set_3d_object.

Input Schema

TableJSON Schema

Name	Required	Default
`angle`	No
`pivot`	No
`space`	No	local
`action`	Yes
`detail`	No	summary
`matrix`	No
`vector`	No
`replace`	No
`scene_id`	Yes
`quaternion`	No
`object_index`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations by explaining composition order, local vs world space, pivot resolution, undo depth, absolute replacement, and invert/reset behavior. These are exactly the non-obvious behavioral details an agent needs.

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?

Dense but every sentence earns its place; no fluff or repetition. The most important scoping statement is front-loaded, and subtle coordinate-space/matrix details are packed efficiently.

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?

For a complex 11-parameter transform tool, the description covers coordinate spaces, pivot centers, undo limits, absolute transforms, and verification steps. The output schema exists to handle return-value details, so the description is complete for invocation.

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

Parameters5/5

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

With 0% schema description coverage, the description carries the full burden and succeeds: vector semantics, axis-angle behavior, quaternion normalization, column-major matrix layout, pivot defaults, and space composition are all explained precisely. Only minor details like the 'detail' parameter are left implicit.

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 clear verb and resource: 'Transform one cloud/mesh' with explicit non-goals ('without changing source files or camera'). It enumerates the action set and distinguishes the tool from appearance-related siblings by pointing to set_3d_object.

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?

Provides clear context for when to use the tool and explicitly routes appearance work to set_3d_object. It also advises verifying with inspect local_to_world, though it does not enumerate a full when-not-to-use list for other sibling tools.

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