Skip to main content
Glama

getShippingQuote

Call when the human asks “how much”, local currency (AUD/£/€), or shipping to a country. Soft AE freight in USD + price.approxLocal (display-only). Pass shipToCountry ISO-2 (AU/US/GB/…). Do not invent FX. Final shipping is set on PayPal — this is an estimate only.

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": {
      "productId": "<productId>",
      "shipToCountry": "<shipToCountry>"
    },
    "name": "getShippingQuote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNo
productIdYesProduct id or slug
shipToCountryYesISO country code, e.g. AU, US, GB

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses several non-obvious traits: rates are soft AE freight in USD, price.approxLocal is display-only, FX must not be invented, and the number is non-binding. It omits auth requirements, rate limits, and how unsupported countries are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the trigger condition, but it opens with usage rather than purpose and the phrase "Soft AE freight" is undefined jargon that an agent cannot decode. Each sentence does carry information, so waste is low even though phrasing is cryptic.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter, no-annotation, no-output-schema tool, the description covers the estimate-only semantics and currency display but says nothing about the response shape or about quantity handling. An agent knows when to call it but not fully what it will get back.

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 67%, with productId and shipToCountry already documented; the description only restates shipToCountry's ISO-2 format and example values. The quantity parameter remains undocumented in both schema and description, including whether it defaults to 1.

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 the tool produces a shipping price estimate for a product shipped to a given country, including a local-currency display field. The verb is implied by the name rather than stated outright and no sibling is named, but the resource and scope are unambiguous enough to distinguish it from checkout tools.

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 concrete trigger conditions ("when the human asks 'how much', local currency… or shipping to a country") and an explicit boundary: final shipping is set on PayPal, so this is an estimate only. It does not name a concrete alternative tool for the final charge, but the PayPal reference serves as the hand-off point.

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