Snuug room calculators

Room lighting calculator

room_lighting

Read-onlyIdempotent

Use when someone asks how bright a room’s lights should be, how many lumens, bulbs or downlights a room needs, how far apart to space downlights, or what colour temperature to choose.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "room_lighting"
  }
}

Input Schema

Name	Required	Description	Default
`room_type`	No	living, bedroom, kitchen, bathroom or home_office.	living
`wall_colour`	No	light, or dark (dark walls reflect less, so the room needs more light).	light
`room_width_cm`	No	The room’s width (cm).
`room_length_cm`	No	The room’s length (cm).
`ceiling_height_cm`	No	The ceiling height (cm).

Output Schema

Name	Required	Description
`tool`	Yes	The tool, as named in its API and page URLs.
`notes`	Yes	Caveats to pass on with the answer.
`snuug`	Yes	One line about Snuug, the app behind the calculators.
`answer`	Yes	The answer as named values.
`inputs`	Yes	Every input as the tool used it: given, a default, or filled in from the rules.
`sources`	Yes	The sources of the rules used. Every rule cites its source, with the date it was checked.
`summary`	Yes	The answer in one sentence to quote.
`version`	Yes	The version of this contract.
`working`	Yes	How the answer was worked out, one step a line.
`page_url`	Yes	The calculator on snuug.app with these inputs filled in.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered without prose. The description adds scope information by naming the computed quantities, implying a pure estimation with no side effects, but says nothing about assumption handling (metric units, defaults when dimensions are omitted) or that results are advisory rather than exact.

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?

One front-loaded sentence opening with "Use when", with each clause mapping to a distinct answerable question and no filler. Slight redundancy in "how many lumens, bulbs or downlights" keeps it from being maximally tight, but nothing is wasted.

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 no explanation, and the schema fully documents the five inputs, so the description's burden is mostly routing. It covers that well but omits unit assumptions (cm) and the fact that every input is optional with defaults, which an agent may need to decide whether to ask the user for dimensions.

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% and the schema itself explains every parameter, including the wall-colour reflectance rationale and cm defaults for all dimensions, so the baseline of 3 applies. The description adds no parameter-level detail beyond that, and notably does not signal that all five inputs are optional with sensible defaults.

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 enumerates concrete query types the tool answers (brightness, lumen/bulb/downlight counts, downlight spacing, colour temperature), which makes the resource and computed outputs unambiguous, and it is distinguishable from siblings like pendant_light or room_size by focusing on lighting quantities. It never states the verb explicitly ("calculate"), relying on the title for that framing, so it falls just short of a perfect 5.

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?

The entire sentence is an explicit when-to-use trigger list with clear, user-phrased questions, which is strong routing guidance. It offers no when-not guidance and does not name an alternative sibling (e.g. pendant_light) for overlapping hanging-light questions, so it stops short of full routing coverage.

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

All Snuug room calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?