Skip to main content
Glama

Configure a blind

configure_product
Read-only

Lock in a full blind specification: product, dimensions, colour, and mount type (inside recess or outside face-fix). Validates that the colour exists and is in stock, then prices the blind. Returns a configuration summary to pass directly into create_cart. Call check_colour_stock first if availability is uncertain. Duo Roller: colour is one blockout and one sheer written "Blockout + Sheer" (get_product returns duo_fabrics).

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>",
      "colour": "<colour>",
      "mount_type": "<mount_type>"
    },
    "name": "configure_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
colourYesColour name (must match available colours)
finishNoOptional finish for aluminium venetians
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.
provinceNoOptional. Customer's South African province or city. Garden Route locations get Duncan's direct contact; other locations get the online shop contact.
quantityNoNumber of blinds (default 1)
width_mmYesWidth in millimetres
height_mmYesHeight/drop in millimetres
mount_typeYesUse inside (recess) or outside (face-fix); handler requires a nonempty value
product_idYesproduct_id from search_catalog or lookup_catalog

Output Schema

NameRequiredDescriptionDefault
colourYes
finishNo
limitsNo
contactNo
summaryNo
currencyYes
deliveryNo
in_stockNo
quantityYes
width_mmYes
height_mmYes
lead_timeNo
next_stepNo
price_zarNo
mount_typeYes
product_idYes
product_nameNo
vat_includedNo
unit_price_zarYes
total_price_zarYes
effective_width_mmNo
effective_height_mmNo
minimum_charge_appliedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this by clarifying the tool prices and validates but returns a summary for create_cart, i.e. no state is written. It also discloses the in-stock colour validation step, which is real behavior beyond the annotations. Minor gap: it does not say what happens on validation failure.

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?

Front-loaded with the core action, then validation/pricing behavior, then downstream handoff, then the edge case. Every sentence carries information. The Duo Roller sentence is niche but prevents a real formatting error, so it earns its place.

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 format need not be explained, and the description still tells the agent the output feeds create_cart. Optional params (finish, no_drill, province, quantity) are left entirely to the schema, which is acceptable at 100% coverage but leaves no cross-parameter guidance on no_drill compatibility.

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 baseline is 3, but the description adds meaning the schema does not: colour must exist and be in stock, mount_type is recess vs face-fix, and the Duo Roller colour must be written "Blockout + Sheer". That last constraint is operationally critical and appears nowhere in the schema.

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 ("Lock in a full blind specification") and enumerates the inputs it covers: product, dimensions, colour, mount type. It is clearly separable from siblings like check_colour_stock (validation-only) and create_cart (persistence), because the description says it returns a summary rather than creating anything.

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?

Gives explicit sequencing: call check_colour_stock first when availability is uncertain, and pass the result into create_cart. That routes the agent across siblings well. It stops short of a full when-not-to-use statement (e.g. what to do if validation fails), so it is strong but not exhaustive.

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