Skip to main content
Glama

Get price for a size

get_price
Read-only

Get an exact ZAR price using product_id from search_catalog or lookup_catalog, width_mm and height_mm. Prices include VAT and delivery. Colour selects the bamboo price tier where applicable. A price is not a stock reservation: validate the exact colour and mount with configure_product before creating a cart. Failure can return success:false or a JSON-RPC validation error.

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": "get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
colourNoOptional bamboo colour for colour-specific tier pricing
finishNoOptional finish for aluminium products: Plain, Brushed, Woodgrain
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 (e.g. 1200)
height_mmYesHeight/drop in millimetres (e.g. 1500)
product_idYesproduct_id from search_catalog or lookup_catalog (e.g. roller-blockout)

Output Schema

NameRequiredDescriptionDefault
finishNo
limitsNo
contactNo
currencyYes
deliveryNo
quantityYes
width_mmYes
height_mmYes
lead_timeNo
next_stepNo
product_idYes
product_nameNo
vat_includedYes
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.8/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint=false, it discloses that prices include VAT and delivery, that colour selects the bamboo price tier, that no stock is reserved, and that failures can surface as success:false or a JSON-RPC validation error. That is meaningful behavioral context annotations cannot carry.

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 verb, resource, and required inputs, and every sentence carries operational value. It is densely packed with semicolons and could be split for readability, but nothing is filler.

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

Completeness5/5

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

A priced-quote tool with an output schema, 8 params fully documented in the schema, and preconditions plus failure modes spelled out in the description. Nothing an agent needs to call it correctly is missing.

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 the origin of product_id ('from search_catalog or lookup_catalog') and clarifies colour's role in tier pricing, which the schema only hints at. The finish/no_drill/province semantics remain solely 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 ('Get an exact ZAR price') plus the required inputs and output currency. It is immediately distinguishable from configure_product and catalog lookup tools by naming them as sources/preconditions.

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

Usage Guidelines5/5

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

Explicitly routes the agent: obtain product_id from search_catalog or lookup_catalog first, then call this; then validate exact colour and mount with configure_product before creating a cart. It also states what this tool is not (a stock reservation), which is exactly the when-not guidance an agent needs.

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