3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Change points of view

edit_cameras

Destructive

Control 3D viewpoints: recall stored camera views, return to the orbit view, and save or delete named perspectives using position, yaw, pitch, and field-of-view settings.

Instructions

Change the points of view. view {i} shows stored view i in the 3D window; aerial returns to the orbit view; store {name?,x?,y?,z?,yaw?,pitch?,fov?,look_at?:[x,y,z]} saves one (missing values from the visitor; yaw 0 looks toward +y/plan bottom, 90 toward -x; pitch positive looks down); delete {i}. cm and degrees. The list is the cameras tool.

Input Schema

TableJSON Schema

Name	Required	Description
`i`	No	Stored view index
`x`	No	Eye position on the plan, cm
`y`	No	Eye position on the plan, cm (y grows down)
`z`	No	Eye height cm
`fov`	No	Horizontal field of view, degrees
`yaw`	No	Direction the eye looks, degrees clockwise on the plan
`name`	No	For `store`: the view's name (default "Ponto de vista N")
`pitch`	No	Degrees down
`action`	No	What to do with the points of view
`look_at`	No	For `store`: point `[x,y,z]` cm to look at (sets yaw and pitch)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`v`	No
`ok`	Yes
`ids`	No
`rev`	No
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv3.0.0Sep 30, 2026
- changedInput schema / properties / action / description
```
Previous value: -"`view`, `aerial`, `store` or `delete`"New value: +"What to do with the points of view"
```
- addedInput schema / properties / action / enum
```
Added value: +[
+  "view",
+  "aerial",
+  "store",
+  "delete"
+]
```
- removedOutput schema / properties / ids / description
```
Removed value: -"Ids created or touched"
```
- removedOutput schema / properties / ok / description
```
Removed value: -"Always true"
```
- removedOutput schema / properties / rev / description
```
Removed value: -"Plan revision"
```
- removedOutput schema / properties / text / description
```
Removed value: -"The reply as written"
```
- removedOutput schema / properties / v / description
```
Removed value: -"Plan version written to, when there are several"
```
First observedv0.1.0Sep 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, covering the safety profile. The description adds convention context (yaw/pitch orientation, cm/degrees, 'missing values from the visitor' defaults) but never states that 'delete' permanently destroys a stored view or what happens to indices after deletion. Adequate but thin beyond the annotations.

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?

Highly front-loaded and dense, with no filler sentences; action semantics are packed into a compact block. The telegraphic style ('delete {i}. cm and degrees.') risks ambiguity, but every clause carries 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?

With 10 parameters, a multi-value enum, and an output schema already present, the description covers all four action branches and the coordinate conventions well. Gaps are minor: no note on post-delete indexing or error behavior for invalid indices.

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?

Schema coverage is 100% so the baseline is 3, but the description genuinely exceeds it: it maps which parameters belong to 'store', defines yaw 0 as +y/plan bottom and 90 toward -x, states pitch positive looks down, and specifies cm/degrees units and the default view name.

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?

States a specific verb+resource ('Change the points of view') and enumerates the four modes of operation (view, aerial, store, delete). It implicitly distinguishes itself from the read-only 'cameras' sibling by pointing to it for the list, though it never names the contrast in the purpose line itself.

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?

Enumerates each action and its effect, and explicitly routes the agent to the 'cameras' tool for listing. However, it gives no guidance on prerequisites (e.g., whether a view index must exist before delete) or when aerial is preferable to a stored view.

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