Snuug room calculators

Room size calculator

room_size

Read-onlyIdempotent

Use when someone asks for a room’s floor area, perimeter, volume or carpet and skirting amounts, or what a size such as 3 × 4 m or 12 × 12 ft means (a box room, a single or double bedroom). Handles L-shaped rooms and bay windows.

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_size"
  }
}

Input Schema

Name	Required	Description	Default
`bay`	No	A bay window in the front wall: none, square (sides at 90°) or angled (sides at 45°, the usual UK canted bay).	none
`doors`	No	Doorways, left out of the skirting.
`shape`	No	rectangle, or l_shape (a second part on the right-hand wall, flush with the far corner).	rectangle
`bay_depth_cm`	No	How far the bay sticks out (cm).
`bay_width_cm`	No	The bay’s width at the wall (cm).
`room_width_cm`	No	The room’s width (along the window wall) (cm).
`part2_depth_cm`	No	An L-shaped room’s second part: how far it sticks out (cm).
`room_length_cm`	No	The room’s length (cm).
`part2_length_cm`	No	An L-shaped room’s second part: its length along the main room (cm).
`ceiling_height_cm`	No	The ceiling height, for the volume (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

A4/5.0

Behavior4/5

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

Beyond the annotations, it discloses relevant capabilities such as handling L-shaped rooms and bay windows, and computing carpet and skirting amounts. It does not cover limitations or unit-conversion behavior, but the output schema and full parameter descriptions reduce that burden.

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?

It is two tightly written sentences with the primary usage trigger front-loaded and no filler. Every clause contributes either a use case or a capability.

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?

For a ten-parameter calculator with an output schema and rich schema descriptions, the description covers the main use cases and special shapes adequately. A minor gap is that it does not clarify that input dimensions are in centimetres even though it gives examples in metres and feet.

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 all ten parameters have clear descriptions, defaults, ranges, and enums. The tool description adds use-case context but little additional parameter meaning beyond the schema.

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 states a specific resource and set of outputs: a room's floor area, perimeter, volume, carpet and skirting amounts. It is clear what the tool does, but it does not explicitly differentiate itself from nearby tools such as home_size or rug_size.

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 gives an explicit 'Use when' trigger with concrete examples, including room dimensions and room-type interpretations. It does not state when not to use it or name alternative sibling tools.

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?