Skip to main content
Glama

Storewire Lite demo store

Get delivery options for a city

get_delivery_options
Read-onlyIdempotent

Delivery to a city as the Trailhead Supply checkout offers it right now: the delivery zone the city belongs to (matched_city=false means the catch-all rate applies), each courier option with its fee in USD and delivery time, the order total above which delivery is free, and whether same-day delivery is available today, with the reason when it is not. With a product (and quantity) same-day can account for that product's stock; with a basket subtotal each fee is the one that basket would pay.

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": {
      "city": "<city>"
    },
    "name": "get_delivery_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNoQuantity of the product (default 1).
cityYesThe delivery city as the shopper writes it.
localeNoAnswer language: en (default en). Names, labels and URLs follow it.
productNoThe product: its public_id from an earlier answer, its page URL or slug on the store's website, or the manufacturer model number.
subtotalNoBasket subtotal in USD: each fee is then what that basket pays.

Output Schema

NameRequiredDescriptionDefault
urlYesThe store's delivery terms page.
cityYes
zoneYes
optionsYes
same_dayYes
truncatedNoPresent and true only when the answer outgrew the size budget and its last list items were left out; ask narrower to see them.
free_aboveYesOrder total in USD from which delivery is free; null when there is none.
answer_typeNoWhat this answer is, for rendering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: the catch-all rate when matched_city=false, that fees are in USD with delivery times, that same-day availability is evaluated 'today' and carries a reason when unavailable, and that same-day can depend on product stock. It does not discuss caching, rate limits, or error behavior for unservable cities.

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 promise ('Delivery to a city as the checkout offers it right now') and then enumerates what comes back. It is dense and the second sentence reads as a run-on, but nearly every clause carries information an agent needs; nothing is filler or restated from the title.

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?

With an output schema present and 100% schema coverage, the description need not re-specify return shapes, yet it covers the modes, the fallback-zone semantics, and same-day reasoning. Minor gaps remain around what happens for an unserved city and how this connects to the cart flow, but for a 5-parameter read-only lookup it is close to sufficient.

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 a baseline of 3 applies, but the description genuinely adds meaning the schema cannot: it explains the relationship between product+qty and subtotal (each fee becomes the one that basket would pay) and decodes matched_city=false as the catch-all rate applying. That mutual-exclusivity/mode framing is not visible from the flat property list.

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 plus scope: it returns delivery zones, courier fees in USD, delivery times, free-delivery threshold and same-day availability for a given city as the checkout currently offers them. An agent can distinguish this from every sibling (cart_*, get_product, search_products) without opening a schema, since none of them describe delivery pricing.

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

Usage Guidelines3/5

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

The second sentence explains the two operating modes — pass a product (plus qty) for stock-aware same-day, or a subtotal for basket-accurate fees — which is useful selection guidance among inputs. It never states when to prefer this tool over alternatives (e.g. before cart_add_item, or versus get_store_info), nor any exclusions or prerequisites, so usage is implied rather than directed.

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.