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 80mm; Duo Roller 115mm), 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. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, and the description reinforces this with 'Changes nothing and returns no price' while disclosing that problems are must-fix versus warnings that require asking the customer. That severity distinction is real behavioural context the annotations cannot convey. It does not discuss latency, error handling or what happens with contradictory inputs (e.g. no_drill plus outside mount).

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 in the first sentence, but the second is a long run-on packed with parenthetical dimension lists and rule enumerations that duplicate the no_drill schema description. The information is useful but not efficiently structured.

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 detailing every return field (ok, problems, warnings, advice) is partly redundant, but the severity semantics are genuinely clarifying. Coverage of inputs, purpose and side-effect profile is sufficient for a 9-parameter read-only validation tool, though the absence of any failure-mode description leaves a minor gap.

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%, so the schema already documents every parameter, including the no_drill rules and mount_type meanings, and the description largely repeats those rules in prose. It adds little per-parameter meaning beyond what the schema states, so the baseline of 3 applies.

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 opening clause gives a specific verb, resource and timing: 'Check a customer's sizes before pricing.' An agent can distinguish this from get_price or configure_product because it is explicitly a pre-pricing validation. It stops short of naming a sibling it replaces or supersedes, so a 5 is not warranted.

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?

'Before pricing' establishes clear call context, and the preconditions are implicit in the schema (product_id from search_catalog or lookup_catalog, mount_type). There are no explicit when-not conditions or named alternatives, so it sits below the top band.

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.