3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Show what the plan displays

disciplines

Read-only

Review electrical and plumbing plan layers to see the active category, hidden items, layer contents, and grouped quantities by catalog kind.

Instructions

Electrical and plumbing projects and plan layers over the plan. active (default): {active, hidden, layers {key:{pieces, hidden}}} — the discipline new symbols go to, what is hidden, and the layers (lighting, appliances, joinery); home gives each piece its plan_layer. quantities: {electrical:[[kind,count,names?]], plumbing:[...], lines_cm:{...}} — grouped by catalog kind (every low outlet together), with the names of the points as the detail. Change what is shown with edit_disciplines.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	No	Default `active`

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: -"`active` (default) or `quantities`"New value: +"Default `active`"

addedInput schema / properties / action / enum

Added value: +[
+  "active",
+  "quantities"
+]

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

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and closed-world behavior. The description adds meaningful context by explaining what each action reveals (the active discipline, hidden elements, layers, grouped quantities) and reinforces that changes belong to edit_disciplines. No auth or rate-limit details, but the added return semantics are useful.

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 content is dense and informative but not optimally front-loaded; the first sentence is a fragment and the return shapes are embedded mid-description. It is reasonably efficient but could be structured more clearly for an agent scanning for the tool's purpose.

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 a single optional parameter, full schema coverage, annotations, and an output schema, the description provides enough context to call the tool correctly. It explains both actions and the alternative for mutation, though it does not elaborate on sibling differentiation beyond edit_disciplines.

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. The description goes further by detailing the two enum values: what 'active' returns (discipline, hidden state, layers) and what 'quantities' returns (grouped counts with names). This adds genuine meaning beyond the schema's brief 'Default active'.

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 description identifies the resource (disciplines, plan layers) and explains what each action returns, distinguishing it from the mutating sibling edit_disciplines. The opening sentence is a noun phrase rather than a clear verb+resource, but the title and action breakdown make the read-only purpose evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly points to edit_disciplines for changing what is shown, giving one clear alternative for mutation. However, it does not say when to choose this tool over other read siblings like show_plan, electrical, or plumbing, leaving usage largely implied.

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