Skip to main content
Glama

Alshhbaa Brassware Store — نحاسيات الشهباء

Validate Shopping Cart & Quote Shipping

validate_cart
Read-only

Use before checkout to verify selected product IDs and quantities against live inventory and prices. Returns validated line items, 15% VAT-inclusive SAR subtotal, shipping fee, grand total, and the checkout handoff URL.

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": {
      "items": "<items>"
    },
    "name": "validate_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesCart line items to validate.

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

readOnlyHint=true is consistent with 'verify' and the description adds useful shape beyond the annotation: it enumerates what comes back (validated line items, 15% VAT-inclusive SAR subtotal, shipping fee, grand total, checkout handoff URL). However, it says nothing about what happens when an item is out of stock, discontinued, or has a changed price — the behaviour an agent most needs to anticipate from a validator.

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?

Two sentences, zero filler, and the highest-value information (when to call, what it checks) comes before the return-value inventory. Nothing could be cut without losing meaning.

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 the return enumeration is a bonus rather than a requirement, and the description still covers trigger, validation target, and currency/tax treatment. The remaining hole is failure semantics — how invalid or unavailable items are surfaced — which matters for a pre-checkout gate.

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% and the single items parameter is fully documented down to nested productId and quantity, so the baseline is 3. The description restates that the IDs and quantities are 'selected' and validated live but adds no constraint, format, or limit information beyond the schema.

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?

States a specific verb and resource: verify selected product IDs and quantities against live inventory and prices, with the trigger point 'before checkout' front-loaded. It is clearly distinct from lookup-style siblings like get_product_details or search_products, though no sibling is named explicitly.

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?

'Use before checkout' gives an explicit when-to-use condition anchored to a workflow stage. There is no statement of when not to use it, no mention of alternatives for re-checking prices, and nothing about repeated calls or already-validated carts.

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.