Skip to main content
Glama

Pattern-repeat wallpaper rolls

bpj_material_wallpaper_repeat
Read-onlyIdempotent

Estimate drops and rolls for straight-match wallpaper by rounding each drop to a whole pattern repeat.

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": {
      "wall": "<wall>",
      "height": "<height>",
      "rollWidth": "<rollWidth>",
      "rollLength": "<rollLength>",
      "repeat": "<repeat>"
    },
    "name": "bpj_material_wallpaper_repeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
wallYes
heightYes
repeatYes
rollWidthYes
rollLengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 adds genuine method detail (each drop rounded up to a whole repeat), but omits whether waste/overage is included, how drops are derived from wall run and roll width, and what the result represents.

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?

A single sentence with no filler, and the key method constraint is front-loaded. It is efficient, though its terseness leaves the tool under-explained rather than over-explained.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five required undocumented numeric parameters and no output schema, the description should explain units, how drops are derived, and what the returned quantities are. Instead it supplies only a one-line method statement, leaving the agent to guess at the calculation's inputs and output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% – all five parameters carry only bare titles with units. The description clarifies the role of 'repeat' (rounding each drop up to a whole pattern repeat) but never explains what 'wall' means (run length), how rollWidth/rollLength are applied, or how drops are computed, so it only partially compensates for the coverage gap.

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 verb and resource ('Estimate drops and rolls') plus the method used ('straight-match wallpaper', 'rounding each drop to a whole pattern repeat'), which is enough for an agent to tell it apart from generic material calculators. It does not explicitly contrast with other wallpaper-related siblings such as roll-remaining calculators, but the purpose is unambiguous.

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?

Usage is implied by the qualifier 'straight-match' – the agent can infer this applies to wallpapers with a repeating pattern matched at seams, not random/free match. However, there is no explicit when-to-use, when-not-to-use, or named alternative, so the agent must infer the boundary conditions itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.