Snuug room calculators

Curtain size calculator

curtain_size

Read-onlyIdempotent

Use when someone asks what size curtains, curtain pole or track to buy, how high to hang a curtain pole, or which UK ready-made curtain size fits a window. Returns the pole’s length and height, the ready-made pair and the made-to-measure sizes.

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

Input Schema

Name	Required	Description	Default
`length`	No	Where the hem ends: sill, below_sill, floor or puddle (on the floor).	floor
`fitting`	No	pole or track.	pole
`heading`	No	The curtain heading: eyelet, pencil_pleat or tab_top.	eyelet
`fullness`	No	The curtains’ total flat width ÷ the pole’s length; default the heading’s usual (2, or 1.5 for tab top).
`sill_height_cm`	No	The sill’s height from the floor (cm).
`window_width_cm`	No	The window’s width, outside the frame (cm).
`window_height_cm`	No	The window’s height, outside the frame (cm).
`ceiling_height_cm`	No	The ceiling’s height from the floor (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.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds useful behavioral context by enumerating the computed outputs and flagging that ready-made sizing is UK-specific, but says nothing about assumptions or units of the returned values.

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: the first front-loads the user-question triggers, the second states the return values. No filler and no repetition of the title.

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, the description needn't explain return shapes, and the annotations cover safety. It is nearly complete, though it could note that all inputs are optional with typical-room defaults, which matters for an 8-parameter calculator.

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 eight parameters carry enum values, defaults, ranges and explanations, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond the implicit UK context, which fits the baseline of 3.

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 exact resource (curtains, curtain pole or track) and the specific outputs returned: pole length and height, ready-made pair, and made-to-measure sizes. It is unambiguously a curtain sizing calculator, easily separated from siblings like rug_size or sofa_fit by resource.

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 explicit trigger conditions ('what size curtains... to buy', 'how high to hang a curtain pole', 'which UK ready-made curtain size fits a window'), which is strong when-to-use guidance. It stops short of any when-not or named alternative, though no sibling appears to overlap this resource.

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?