Skip to main content
Glama

Prepare a price-match request

request_price_match
Read-only

Submit a price match claim when the customer has found the same blind at a lower price elsewhere. Custom Blinds matches verified South African retailer prices for identical product, dimensions, and specs. Returns a pre-filled WhatsApp link to the claims team. Not applicable to clearance or flash-sale prices, international retailers, or items out of stock at the other retailer. Requires product_id and competitor_price_zar at minimum.

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>",
      "competitor_price_zar": "<competitor_price_zar>"
    },
    "name": "request_price_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
width_mmNoWindow width in mm
height_mmNoWindow height/drop in mm
product_idYesProduct the customer wants to match (e.g. roller-blockout)
customer_nameNoCustomer name
competitor_urlNoURL to competitor product page or quote
competitor_nameNoName of the other retailer
customer_whatsappNoCustomer WhatsApp number for follow-up
competitor_price_zarYesCompetitor's price in ZAR (incl. VAT)

Output Schema

NameRequiredDescriptionDefault
noteYes
messageYes
successYes
exclusionsYes
whatsapp_urlYes
claim_summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, and the description reinforces this by explaining the tool returns a pre-filled WhatsApp link rather than performing the claim itself. It adds eligibility rules and the return artifact, though the word 'Submit' is slightly at odds with a read-only preparation step and could be clearer about no claim being filed automatically.

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

Conciseness5/5

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

Four tight sentences: purpose first, then matching policy, then the return value, then exclusions and required inputs. No filler and the most decision-relevant information is front-loaded.

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?

An output schema exists, so return values need not be detailed, yet the description still names the WhatsApp link artifact. Combined with eligibility rules and required inputs, an agent has everything needed to decide and invoke correctly.

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 coverage is 100%, so every parameter is already documented in the schema. The description only restates the two required fields, adding no format or usage detail beyond what the schema provides, so the baseline 3 applies.

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 ('Submit a price match claim') plus the domain constraint (identical product, dimensions, specs, South African retailers). An agent can distinguish this from get_price or create_quote_link without opening the schema.

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?

Gives explicit when-to-use ('customer has found the same blind at a lower price elsewhere') and explicit exclusions (clearance, flash-sale, international retailers, out-of-stock items). It also names the minimum required inputs, so the agent knows the gating conditions before calling.

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