3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Show or hide disciplines

edit_disciplines

Select electrical, plumbing, or architecture to dim other plan elements, or show/hide lighting, appliance, and joinery layers to control what appears in the plan, exports, and 3D.

Instructions

Change what the plan shows. select {d: electrical|plumbing|architecture}: new symbols (catalog cat electrical/plumbing) and lines go there and the rest is dimmed; select architecture hides the electrical and plumbing projects (show brings one back); select a project shows it with the architecture dimmed. show/hide {d}, where d can also be a layer of the plan — lighting (lamps, spots, LED), appliances (fridge, stove, oven, hood, washer…) or joinery (cabinets, wardrobes, countertops): hidden from the plan, its exports and the 3D. The 3D follows the plan unless show_all_3d=true, which makes it show everything. Pieces are in a layer by what they are; update(layer=lighting|appliances|joinery|none) overrides it. What is shown now is the disciplines tool.

Input Schema

TableJSON Schema

Name	Required	Description
`d`	No	`electrical`, `plumbing` or `architecture`; for show/hide also a plan layer: `lighting`, `appliances` or `joinery`
`action`	No	What to do with discipline `d`
`show_all_3d`	No	Whether the 3D shows everything (true) or hides what the plan hides (false). Applies with any action

Output Schema

TableJSON Schema

Name	Required	Description	Default
`active`	No
`hidden`	No
`layers`	No
`lines_cm`	No
`plumbing`	No
`electrical`	No
`show_all_3d`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv3.0.0Sep 30, 2026

changedInput schema / properties / action / description

Previous value: -"`select`, `show` or `hide`"New value: +"What to do with discipline `d`"

addedInput schema / properties / action / enum

Added value: +[
+  "select",
+  "show",
+  "hide"
+]

removedOutput schema / properties / active / description

Removed value: -"Discipline drawn on top: electrical, plumbing, or null"

removedOutput schema / properties / electrical / description

Removed value: -"action=quantities: [kind, count, names?]"

removedOutput schema / properties / hidden / description
```
Removed value: -"Disciplines hidden"
```

removedOutput schema / properties / layers / description

Removed value: -"Plan layers: {lighting, appliances, joinery} → {pieces, hidden}"

removedOutput schema / properties / lines_cm / description

Removed value: -"action=quantities: drawn lines by discipline, cm"

removedOutput schema / properties / plumbing / description

Removed value: -"action=quantities: [kind, count, names?]"

removedOutput schema / properties / show_all_3d / description
```
Removed value: -"Every discipline shown in 3D"
```

First observedv0.1.0Sep 24, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds substantial behavioral context beyond that—new symbols go to the selected discipline while the rest is dimmed, hiding removes items from the plan, its exports and the 3D, and the 3D follows the plan unless show_all_3d=true. This is exactly the operational disclosure a mutating toggle needs.

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

Conciseness3/5

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

The lead sentence is well front-loaded, but the body is a dense semicolon-heavy wall of text mixing actions, layers, 3D behavior and override mechanics, making it hard to parse. Information density is high, but structure and scannability suffer.

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 an output schema present, return values need not be explained, and the description covers the complex discipline/layer/3D interplay, including the update(layer=) override. It is nearly complete for this complexity, though the tangled presentation leaves some edge relationships (e.g., show vs. select on architecture) to inference.

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 adds meaning beyond the schema: it clarifies that d means a discipline for select but may also be a plan layer (lighting/appliances/joinery) for show/hide, and it enumerates what each layer contains. This disambiguates the overloaded parameter in a way the schema does not.

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?

The opening 'Change what the plan shows' gives a specific verb+resource, and the text names what each action (select/show/hide) operates on, distinguishing disciplines from layers. However, the run-on phrasing and the mixed treatment of disciplines vs. layers make the core purpose harder to extract than a clean statement would, so it falls short of the top score.

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?

It explains the effect of each action (select vs. show/hide) and routes the agent to alternatives: update(layer=...) for overriding a piece's layer, and the 'disciplines' tool to see current state. What's missing is an explicit statement of when NOT to use this tool, so it stays at a clear-context, no-exclusions level.

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