Skip to main content
Glama

Request fabric swatches

request_swatch

Log up to 5 colour codes against an EXISTING order for the team (order_ref required; without it the tool returns status order_required and logs nothing). Sample swatches, not off-cuts: on orders over R8,000 the customer can ask on WhatsApp for swatches in the colours they like, for the product they are ordering; if nothing suits, full refund with no fees. Never quote a sample price or courier cost.

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": {
      "customer_name": "<customer_name>",
      "customer_email": "<customer_email>",
      "customer_phone": "<customer_phone>",
      "product_interest": "<product_interest>",
      "order_ref": "<order_ref>"
    },
    "name": "request_swatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburbNoOptional delivery suburb
order_refYesThe order reference the swatches ship with. Required.
swatch_codesNoOptional specific colour codes (max 5)
customer_nameYesCustomer's full name.
customer_emailYesCustomer's email address.
customer_phoneYesUsed as WhatsApp number
product_interestYese.g. 'Roller Blockout' or 'Honeycomb'

Output Schema

NameRequiredDescriptionDefault
policyNo
statusYes
messageYes
next_stepNo
order_refNo
request_idNo
swatch_countNo
estimated_delivery_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real behavior the annotations cannot convey — the exact failure mode and status string when order_ref is missing, the 5-code cap, and the refund-with-no-fees outcome. It does not cover rate limits or confirmation behavior, but that is a minor gap given the output schema exists.

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?

The hard requirement and the failure consequence are front-loaded in the first clause, which is the right ordering. The single dense sentence with stacked parentheticals is harder to scan than it needs to be, and the refund-policy clause, while useful for customer messaging, sits awkwardly mid-sentence.

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?

For a 7-parameter mutation tool with a 5-required-field contract and an output schema, the description covers the key precondition, the cap, and the customer-facing rules. It does not repeat return values, which is appropriate since the output schema exists, leaving only minor gaps around what the tool does with partial or invalid colour codes.

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 all seven parameters are already self-documenting. The description mostly repeats schema facts (order_ref required, max 5 codes) rather than adding new meaning, so the baseline 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 description states a specific verb and resource: 'Log up to 5 colour codes against an EXISTING order', and clarifies the resource is sample swatches, not off-cuts. It is clearly distinguishable from cart/checkout siblings, though it never names a sibling it competes with.

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?

It gives an explicit precondition (order_ref required, otherwise status order_required and nothing is logged) and a business threshold (orders over R8,000, requested via WhatsApp). It also supplies a 'when-not' instruction: never quote a sample price or courier cost. It stops short of pointing to an alternative sibling when the prerequisite fails.

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