Snuug room calculators

Pendant light height and size calculator

pendant_light

Read-onlyIdempotent

Use when someone asks how high to hang a pendant or chandelier over a dining table or kitchen island, how long its drop should be, or what diameter of light suits a table or room.

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": "pendant_light"
  }
}

Input Schema

Name	Required	Description	Default
`place`	No	table (over a table or island) or floor (over open floor or a hall).	table
`lights`	No	Over a table: how many lights in a row (1–3).
`room_width_cm`	No	The room’s width, for the room-size rule (cm).
`room_length_cm`	No	The room’s length, for the room-size rule (cm).
`table_width_cm`	No	Over a table: its width (cm).
`table_height_cm`	No	Over a table: its height (cm).
`table_length_cm`	No	Over a table: its length (cm).
`ceiling_height_cm`	No	The ceiling height (cm).
`fitting_height_cm`	No	The shade’s own height, top to bottom (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.8/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation tool. The description adds the problem domain but no further behavioral context such as assumptions, rounding, or output characteristics beyond what the annotations and output schema cover.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no filler or redundant restatement of the title. Every phrase contributes directly to identifying the use case.

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?

Given that all nine parameters are schema-documented with defaults and ranges, an output schema exists, and annotations cover the safety profile, the description is largely complete for selecting the tool. It could be strengthened with a brief note on what the result represents, but the structured fields carry the remaining burden.

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 every parameter is already documented in the input schema. The description mentions table/island and room contexts but adds no parameter-specific meaning beyond what the schema already provides.

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 clearly states the tool answers pendant/chandelier height, drop-length, and diameter questions for dining tables, kitchen islands, or rooms. It is specific about the resource and calculation intent, but it does not explicitly distinguish itself from related sibling tools such as room_lighting.

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 description gives an explicit 'Use when' condition with concrete scenarios: hanging height, drop length, and diameter sizing. It does not name alternatives or state when not to use this tool, so it falls short of full alternative routing.

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?