Snuug room calculators

Wallpaper calculator

wallpaper_rolls

Read-onlyIdempotent

Use when someone asks how many rolls of wallpaper they need for a room, some walls or one feature wall, including a pattern repeat and a straight or offset match.

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

Input Schema

Name	Required	Description	Default
`mode`	No	room (all four walls), walls (some walls) or feature (one wall).	room
`doors`	No	Doors, each saving a drop (default 1 for a room, else 0).
`match`	No	free (or plain), straight or offset (half-drop).	free
`trim_cm`	No	Extra on each drop for trimming (default 10 cm) (cm).
`spare_rolls`	No	Spare rolls from the same batch (default 1).
`roll_width_cm`	No	The roll’s width (default 53 cm) (cm).
`room_width_cm`	No	For a room: its width (cm).
`wall_width_cm`	No	For walls or a feature wall: the width, the walls added up (cm).
`roll_length_cm`	No	The roll’s length (default the UK standard, 1005 cm) (cm).
`room_length_cm`	No	For a room: its length (cm).
`wall_height_cm`	No	The wall height, skirting to ceiling (cm).
`pattern_repeat_cm`	No	The pattern repeat, from the label (0 for none) (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 the safety profile needs no restatement. The description adds domain context that the result is an advisory roll count covering pattern repeat and match type. It does not mention that defaults are assumed when parameters are omitted, which is the one behavioral detail an agent might want given 12 all-optional parameters.

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?

It is a single front-loaded sentence that puts the trigger before the qualifications, with no filler. It is slightly dense because it packs three modes and two pattern conditions into one clause, 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?

An output schema exists, so return values need not be explained, and the annotations carry the safety semantics. The description covers the three operating modes and the pattern-match dimension, which is the conceptual load for a 12-parameter calculator. A brief note that unspecified parameters fall back to standard UK defaults would make it complete.

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%, with every parameter carrying a unit, default, range and mode-conditional note, so the schema already does the heavy lifting. The description only echoes the match-type vocabulary ('straight or offset match') that the enum defines. Under the coverage rule this is a baseline 3.

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 names a specific outcome (how many rolls of wallpaper) and enumerates the three scopes it handles (room, some walls, one feature wall), plus the pattern-repeat/match complication. It is clearly distinct from siblings like paint_quantity or curtain_size by resource. It stops short of an explicit 'calculates X' verb form, but an agent can still tell what it returns.

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 opening clause is an explicit trigger condition ('Use when someone asks how many rolls...'), which is stronger than most definitions. It also signals that pattern repeat and straight/offset match are in scope, so the agent knows to supply those. It offers no when-not guidance or alternative tools for related wall-covering queries, 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?