Skip to main content
Glama

Estimate lead time and delivery

get_delivery_estimate
Read-only

Lead time for a new order. Production takes 5 to 7 working days once payment clears, outside peak seasons. Pass the customer's town and 4-digit street postal_code (province and suburb help) and the transit range is The Courier Guy's own quote from our Knysna depot to that town; without them it is the standard 2 to 5 working days. Returns working-day ranges and a summary safe to share. Never quote a dispatch or delivery date: weather and production set them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_delivery_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoCustomer's town or city, e.g. 'Johannesburg'
suburbNoOptional suburb, e.g. Sandton
provinceNoOptional province, e.g. Gauteng
width_mmNoOptional widest blind in mm (sets the parcel length)
order_dateNoISO date of the order (e.g. '2026-05-18'). Defaults to today.
postal_codeNo4-digit South African STREET postal code, e.g. 2196

Output Schema

NameRequiredDescriptionDefault
summaryYes
importantYes
order_dateNo
destinationNo
transit_noteNo
transit_sourceNo
courier_serviceNo
production_startsNo
expedited_availableNo
courier_high_risk_areaNo
delivery_after_dispatchYes
transit_working_days_maxYes
transit_working_days_minYes
production_working_days_maxYes
production_working_days_minYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, yet the description adds substantial behavior: the 5-7 working-day production window (excluding peak seasons), the 2-5 working-day fallback, that transit comes from The Courier Guy's quote out of the Knysna depot, and that the response is a shareable-safe summary. It even states a prohibition on converting the estimate into a fixed date, which is exactly the kind of behavioral boundary annotations cannot express.

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?

Very information-dense with no filler, but the middle sentence runs long and tangles the conditional logic ('and the transit range is The Courier Guy's own quote from our Knysna depot to that town; without them...'). Front-loading the purpose and the final 'never quote a date' rule works well.

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 read-only estimator with a full output schema, this covers what matters: what drives the number, when the fallback applies, and the quoting constraint. It need not explain return fields since an output schema exists. Only the role of order_date and width_mm is left entirely to the schema.

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, and the description adds only the precision relationship between town/postal_code (exact quote) versus province/suburb (helpful) versus neither (fallback). width_mm and order_date are never mentioned, so half the inputs gain no extra meaning from the prose. Baseline 3 is right.

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?

Opens with a specific noun-verb framing ('Lead time for a new order') and then states concretely what it computes: production time plus a courier transit range. No sibling tool covers delivery estimation, and the description makes the returned artifact (working-day ranges + shareable summary) unmistakable.

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?

Gives clear conditional guidance: pass town and 4-digit postal_code for the courier's own quote, otherwise the estimate falls back to the standard 2-5 working days; province and suburb 'help'. It also sets a hard usage rule ('Never quote a dispatch or delivery date'). It does not name an alternative tool, but the when-to-use context is explicit.

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