3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Rate the lighting

lighting

Read-only

Review room illuminance with photometric calculations and ABNT NBR ISO/CIE 8995-1 residential references, then place or edit fixtures to meet lux targets.

Instructions

Lighting review: lux (illuminance) per room by photometry. Every fixture's flux (lm, or W × lamp efficacy), color temperature and distribution (bulb, spot beam, LED panel/strip) lights the work plane by the inverse-square cosine law, walls casting shadows, plus interreflection (split flux). Reply rooms [[id,name,m²,avg lx,min lx,uniformity,reference lx,fixtures,W/m²,verdict]] against ABNT NBR ISO/CIE 8995-1 residential references. edit_lighting places the fixtures a room needs. Set a piece's light with place/update light {lm|w,lamp,k,beam,area}.

Input Schema

TableJSON Schema

Name	Required	Description
`room`	No	Room id (default: every room of the current storey)
`level`	No	Storey to review, an id like `lv3` (default: the one shown)
`plane`	No	Work plane height cm (default 75)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`W`	Yes
`lm`	Yes
`rooms`	Yes
`sources`	Yes
`fixtures`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv3.0.0Sep 30, 2026

addedInput schema / properties / level

Added value: +{
+  "description": "Storey to review, an id like `lv3` (default: the one shown)",
+  "type": "string"
+}

removedOutput schema / properties / W / description
```
Removed value: -"Total watts"
```
removedOutput schema / properties / fixtures / description
```
Removed value: -"Light fixtures in the plan"
```
removedOutput schema / properties / lm / description
```
Removed value: -"Total lumens"
```

removedOutput schema / properties / rooms / description

Removed value: -"[id, name, m², average lx, minimum lx, uniformity, reference lx, fixtures, W/m², verdict]"

removedOutput schema / properties / sources / description

Removed value: -"Standards cited, by code: [title, tier, url]"

First observedv0.1.0Sep 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description still adds substantial behavioral context: computed metrics, the photometric method (inverse-square cosine law, interreflection split flux), and the ABNT NBR ISO/CIE 8995-1 reference against which verdicts are issued. It omits any performance/cost caveats for a whole-storey sweep.

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 purpose and alternatives are front-loaded, but the middle sentence explaining photometry ('inverse-square cosine law', 'split flux') is physics flavor that does not help the agent decide or invoke correctly, and the reply-column enumeration is largely redundant with the output schema.

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, full parameter coverage, and read-only annotations, the definition is complete: an agent knows the scope (storey/room), the metrics returned, the compliance standard, and the sibling tools that perform edits. Nothing essential for correct invocation is missing.

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 100%, so room/level/plane defaults are already documented. The description reinforces the storey/room scoping but adds no syntax, allowed values, or format details beyond the schema, so baseline 3 is warranted.

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 specific verb (review/rate) on a specific resource (illuminance per room) and explicitly distinguishes itself from edit_lighting (places fixtures) and place/update light (sets a piece's light). An agent can tell it apart from the ~50 siblings without opening a schema.

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?

Routes clearly to alternatives: use edit_lighting to place the fixtures a room needs and place/update light to set a piece's light, which implies this tool is the read-only reviewer. It does not state an explicit when-to-use trigger (e.g. 'call before/after editing to check compliance'), so it stops short of 5.

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