Brush Pack

Wallpaper rolls

wallpaper_rolls

Read-onlyIdempotent

Rolls of wallpaper for a room or feature wall from wall widths (or room length and width), height, roll width and length (default 10.05 x 0.53 m), pattern repeat and match (free, straight, half drop). Shows drops, cut length, drops per roll and rolls, plus one spare. Example: {"length_m":4,"width_m":3.5,"height_m":2.4,"pattern_repeat_cm":53,"pattern_match":"straight"}.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "height_m": "<height_m>"
    },
    "name": "wallpaper_rolls"
  }
}

Input Schema

Name	Required	Description
`trade`	No	Optional. The decorator's own business details (Nero Trade Profile v1). Used to prefill quotes and to give a stable nero_trade_ref. Not stored by Brush Pack.
`width_m`	No	Room width, if papering all four walls.
`height_m`	Yes	Height to paper, metres.
`length_m`	No	Room length, if papering all four walls.
`roll_width_m`	No	Defaults to 0.53.
`pattern_match`	No	Defaults to straight when a repeat is given, otherwise free.
`roll_length_m`	No	Defaults to 10.05.
`wall_widths_m`	No	Width of each wall to paper. For one feature wall give one width.
`deduct_width_m`	No	Width of near full height openings (patio doors, wide windows) to take off.
`pattern_repeat_cm`	No	Pattern repeat from the roll label, cm. 0 or missing means no repeat.
`trim_allowance_cm`	No	Total extra per drop for trimming top and bottom. Defaults to 10.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful behavioral context beyond that: default roll dimensions, pattern match modes, trimming allowance, the one-spare-roll rule, and the specific results returned. It does not cover error handling or calculation caveats, but for this domain the added disclosure is substantial.

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?

The definition is front-loaded with the core purpose and then gives defaults, outputs, and a concrete example. It is dense but every sentence contributes useful calculation context, with no obvious filler.

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?

This is a moderately complex calculator with many optional parameters, a nested trade object, and no output schema. The description compensates by explaining defaults, supported pattern matches, computed outputs, and providing an example call, making it sufficiently complete for an agent to invoke it correctly. The trade object's role is left to the schema, which is acceptable because it is clearly documented there.

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 coverage is 100%, so the schema already documents all 11 parameters, including defaults and enums. The description reinforces key defaults and the room-versus-feature-wall input pattern, but it mostly repeats structured information rather than adding much parameter meaning beyond what the schema provides.

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 specific resource and calculation clearly: wallpaper rolls for a room or feature wall, based on wall dimensions, height, roll size, and pattern details. It also states the computed outputs (drops, cut length, drops per roll, rolls, plus one spare), so an agent can identify the tool's purpose without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by explaining input modes for a room versus a feature wall, and it gives an example call. However, it does not explicitly say when to use this instead of a related tool such as paint_quantity, nor does it state exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Brush Pack 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.