Skip to main content
Glama

Estimate delivery within Australia

estimate_delivery
Read-onlyIdempotent

Whether Printdash delivers to an Australian postcode (or, signed in, a saved address) and, given the jobs being ordered, the delivery fee and the delivered total, priced the way checkout prices it. Australian postcodes only: anywhere else is refused, because Printdash delivers within Australia only. Prices in AUD; totals include GST.

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": "estimate_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobsNoThe jobs being ordered together; the fee depends on the order's value.
postcodeNoAn Australian postcode (four digits) for the delivered price. Printdash delivers within Australia only.
address_idNoSigned in: a saved address id from list_addresses, instead of a postcode.

Output Schema

NameRequiredDescriptionDefault
gstNo
nextNo
linesNo
reasonNo
messageNo
currencyYes
deliverableYes
destinationNo
job_refusedNo
service_areaYes
total_inc_gstNo
shipping_labelNo
shipping_ex_gstNo
subtotal_ex_gstNo
pickup_availableNo
prices_include_gstYes
delivery_unavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / jobs / items / properties / configuration / properties / stickerShape / description
      Added value: +"Where get_product has a sticker_shape field: an id from it. Stickers: square, circle or custom; labels: rectangle, circle or custom."
    • changedInput schema / properties / jobs / items / properties / configuration / properties / stickerShape / enum
      Previous value: -[
      -  "square",
      -  "circle",
      -  "custom"
      -]New value: +[
      +  "square",
      +  "rectangle",
      +  "circle",
      +  "custom"
      +]
  2. 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 safety is covered. The description adds genuine behavioural context beyond that: non-Australian requests are refused, prices are in AUD, totals include GST, and the figures match how checkout prices the order. It does not describe failure modes or partial-job handling, which the schema attributes elsewhere.

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 main purpose in the first clause, then the billing context. It is slightly redundant: 'Printdash delivers within Australia only' appears twice (in the exclusion clause and as the reason), and the AUD/GST note would serve better as a trailing fact. Overall tight, but not waste-free.

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 return-value details need not be described, and the remaining essentials — eligibility scope, currency, tax treatment, and price fidelity to checkout — are all present. Nothing an agent needs in order to call it correctly for the common case is missing.

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 postcode, address_id, and jobs are already documented in detail, including the four-digit postcode rule and the address_id-as-alternative relationship. The description confirms the AUD/GST semantics but adds little else beyond what the schema already says, so baseline 3 is appropriate.

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 compound purpose: eligibility for delivery (by postcode or signed-in address), plus the delivery fee and the resulting checkout-matched total. That is a concrete verb+resource and is distinguishable from ordering tools like create_record-like siblings (e.g., confirm, convert_quote_to_order) because it explicitly says it computes pricing rather than placing an order.

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 a clear use condition and exclusion: use it with an Australian four-digit postcode (or a saved address via address_id from list_addresses when signed in), and it is refused for anywhere outside Australia. It does not name an alternative for pricing a cart, but the eligibility-plus-fee framing makes the intended moment (pre-checkout estimation) inferable.

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