Snuug room calculators

Home size calculator

home_size

Read-onlyIdempotent

Use when someone asks how big a flat or house should be for a number of people or bedrooms, whether a home or bedroom is big enough, or what England’s nationally described space standard requires. England only; it is a planning standard for new homes.

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

Input Schema

Name	Required	Description
`people`	No	The people the home is for (one bed space each).
`storeys`	No	The floors the home has (1 for a flat).
`bedrooms`	No	The number of bedrooms.
`home_area_m2`	No	Optional: the home’s gross internal floor area, to compare with the standard (m²).
`bedroom_1_width_cm`	No	Optional: bedroom 1's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_2_width_cm`	No	Optional: bedroom 2's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_3_width_cm`	No	Optional: bedroom 3's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_4_width_cm`	No	Optional: bedroom 4's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_5_width_cm`	No	Optional: bedroom 5's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_6_width_cm`	No	Optional: bedroom 6's width, with its length. The bedrooms are ranked by floor area before the checks (cm).
`bedroom_1_length_cm`	No	Optional: bedroom 1's length, with its width (cm).
`bedroom_2_length_cm`	No	Optional: bedroom 2's length, with its width (cm).
`bedroom_3_length_cm`	No	Optional: bedroom 3's length, with its width (cm).
`bedroom_4_length_cm`	No	Optional: bedroom 4's length, with its width (cm).
`bedroom_5_length_cm`	No	Optional: bedroom 5's length, with its width (cm).
`bedroom_6_length_cm`	No	Optional: bedroom 6's length, with its width (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

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 the safety profile is fully covered. The description's additional value is the jurisdictional/tenure constraint (England, new homes only), which genuinely affects whether results apply — but it says nothing about how results are computed or what the two check modes return, leaving the rest to the output schema.

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?

Two sentences, both load-bearing: the first front-loads the trigger conditions, the second immediately bounds applicability. No restatement of the title or padding.

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 16-parameter but all-optional calculator with an output schema, the description supplies the purpose, the standard invoked and the geographic/tenure limits — enough to call it correctly. It omits what happens when only some inputs are supplied (which checks run), though the schema's defaults and optional markers largely cover that.

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 one of the 16 parameters is already documented, including defaults, ranges and the note that bedrooms are ranked by floor area before checks. The description only loosely gestures at the inputs ('number of people or bedrooms', 'whether a home or bedroom is big enough'), so baseline 3 applies.

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?

The description names the resource (home/flat floor area, bedroom sizes) and the exact question it answers: how big a home should be for a number of people or bedrooms, and whether a home or bedroom meets England's nationally described space standard. That scope is distinct from siblings like room_size or dining_table_size, and the domain limitation ('England only; a planning standard for new homes') further pins it down.

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 three explicit, distinct trigger conditions ('how big should it be', 'is it big enough', 'what does the space standard require') plus a negative scope: England only and new-build planning standard, not existing homes elsewhere. What is missing is an explicit routing statement naming an alternative tool for out-of-scope cases, so it falls short of a 5.

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?