Skip to main content
Glama

Check blind measurements

validate_measurement
Read-only

Check a customer's sizes before pricing. Returns ok, problems (must fix), warnings (ask the customer) and advice: size limits for the product, product minimums, centimetre slips, inside-mount reveal depth (single rollers 50mm, no-drill rollers included; Double Roller zebra 90mm; Duo Roller 100mm), no-drill rules (inside only, at least 50mm reveal on rollers and 40mm on 25mm venetians, 2000mm max width, 1500mm on 25mm venetians), face-fix sizing (add 100mm each side and 100mm above and below) and the width we deduct when making an inside mount. Changes nothing and returns no price.

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": {
      "product_id": "<product_id>",
      "width_mm": "<width_mm>",
      "height_mm": "<height_mm>"
    },
    "name": "validate_measurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
colourNoOptional exact colour name, checked for stock and width limits
no_drillNoOptional. true for the no-drill option (tension brackets, inside the frame, max 2000mm wide; 1500mm on 25mm venetians). Adds the R65 no-drill kit per blind. Offered on indoor roller blinds, including value rollers, and 25mm aluminium or aluwood venetians. Dedicated no-drill products already include the kit.
width_mmYesWidth the customer will enter, in millimetres
height_mmYesDrop the customer will enter, in millimetres
mount_typeNoinside (in the recess) or outside (face fix)
product_idYesproduct_id from search_catalog or lookup_catalog
opening_drop_mmNoOptional, face fix only: drop of the opening itself
reveal_depth_mmNoOptional depth of the recess in mm, needed for inside mounts and no-drill
opening_width_mmNoOptional, face fix only: width of the opening itself

Output Schema

NameRequiredDescriptionDefault
okYes
adviceYes
limitsNo
no_drillNo
problemsYes
warningsYes
width_mmYes
height_mmYes
next_stepYes
mount_typeNo
product_idYes
product_nameNo
reveal_depth_mmNo
measure_guide_urlYes
production_width_mmNo
inside_mount_min_reveal_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/destructiveHint=false, and the description reinforces this with 'Changes nothing and returns no price'. It goes further by disclosing the domain rules applied (reveal depths of 50/90/100mm, no-drill width caps of 2000mm and 1500mm, face-fix additions of 100mm) and the problems-vs-warnings distinction, which annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the bulk of the description is a single dense sentence with deeply nested parentheses enumerating rule variants. The content is relevant, yet the run-on structure makes it slower to parse than a short bulleted breakdown would be.

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 and annotations covering the safe-read profile, the description need only justify when to call it and what domain rules it enforces, which it does. Minor gaps remain: it does not say how this relates to check_colour_stock for the colour parameter or what to do when results are returned.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds interpretation: it explains what inside-mount and face-fix mean operationally (adding 100mm each side plus 100mm top and bottom, and the width deducted for inside mounts), which clarifies how mount_type, opening_width_mm and opening_drop_mm are meant to be used.

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?

States a specific verb and resource ('Check a customer's sizes') and places it in the workflow ('before pricing'), so an agent can distinguish this pre-flight validation from get_price or check_colour_stock. The sentence also names the returned categories, making the tool's scope concrete.

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?

'Check a customer's sizes before pricing' gives a clear ordering cue, and 'before pricing' implies the alternative that follows it. No explicit when-not-to-use or named sibling alternative is given, so it stops short of full routing guidance.

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.

Resources