Skip to main content
Glama

get_shipping_rates

Get available shipping rates for the cart. Collects shipping address via elicitation if supported.

SKYFIRE TOKEN (optional): Pass a kya or kya-pay token in the skyfire-pay-id header to boost trust score. No token required — request proceeds normally if omitted. PAYMENT MANDATE: this tool also requires one. Send it as the payment_mandate argument if your client cannot set headers, or as an X-Payment-Mandate header. It must carry mandate_id, max_amount_cents, currency, exp, sub, aud, and its currency must match the cart's currency or the call is denied outright. The cap in max_amount_cents is enforced against the cart total. CREDENTIAL: this store needs one. Call the create_sandbox_key tool first (it is in this tool list and needs no credential), then pass the key you get back as the agent_key argument — or as an Authorization: Bearer header if your client can set headers. Do not ask a person to log in: there is no human login for this store.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cart_idYesCart session ID returned by create_cart
agent_keyNoSandbox credential from `create_sandbox_key`. Use this when your client cannot set an `Authorization: Bearer` header.
payment_mandateNoPayment mandate with `mandate_id`, `max_amount_cents`, `currency`, `exp`, `sub`, `aud`. Its `currency` must match the cart's. Use this when your client cannot set an `X-Payment-Mandate` header.
shipping_addressNoDestination address. Omit to collect via elicitation (Claude.ai).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratesYes
cart_idYes
address_cityNo
address_countryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_key
      Added value: +{
      +  "description": "Sandbox credential from `create_sandbox_key`. Use this when your client cannot set an `Authorization: Bearer` header.",
      +  "type": "string"
      +}
    • addedInput schema / properties / payment_mandate
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Payment mandate with `mandate_id`, `max_amount_cents`, `currency`, `exp`, `sub`, `aud`. Its `currency` must match the cart's. Use this when your client cannot set an `X-Payment-Mandate` header."
      +}
  2. Changed4 schema fields changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedInput schema / properties / shipping_address / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / properties / rates / items / additionalProperties
      Previous value: -falseNew value: +true
  3. Changed3 schema fields changed
    • addedOutput schema / properties / rates / items / properties / authoritative
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rates / items / properties / source
      Added value: +{
      +  "enum": [
      +    "platform",
      +    "merchant_policy",
      +    "estimated"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / properties / rates / items / required
      Previous value: -[
      -  "handle",
      -  "title",
      -  "price",
      -  "currency"
      -]New value: +[
      +  "handle",
      +  "title",
      +  "price",
      +  "currency",
      +  "source",
      +  "authoritative"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "address_city": {
      +      "type": "string"
      +    },
      +    "address_country": {
      +      "type": "string"
      +    },
      +    "cart_id": {
      +      "type": "string"
      +    },
      +    "rates": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "currency": {
      +            "type": "string"
      +          },
      +          "estimated_delivery": {
      +            "type": "string"
      +          },
      +          "handle": {
      +            "type": "string"
      +          },
      +          "price": {
      +            "type": "number"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "handle",
      +          "title",
      +          "price",
      +          "currency"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "cart_id",
      +    "rates"
      +  ],
      +  "type": "object"
      +}
  5. Changed4 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties
      Added value: +{
      +  "cart_id": {
      +    "description": "Cart session ID returned by create_cart",
      +    "type": "string"
      +  },
      +  "shipping_address": {
      +    "additionalProperties": false,
      +    "description": "Destination address. Omit to collect via elicitation (Claude.ai).",
      +    "properties": {
      +      "address1": {
      +        "description": "Street address",
      +        "type": "string"
      +      },
      +      "city": {
      +        "description": "City",
      +        "type": "string"
      +      },
      +      "country_code": {
      +        "description": "ISO country code (e.g. US, CA)",
      +        "type": "string"
      +      },
      +      "province_code": {
      +        "description": "Province or state code (optional)",
      +        "type": "string"
      +      },
      +      "zip": {
      +        "description": "Postal / ZIP code",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "address1",
      +      "city",
      +      "country_code",
      +      "zip"
      +    ],
      +    "type": "object"
      +  }
      +}
    • addedInput schema / required
      Added value: +[
      +  "cart_id"
      +]
  6. Changed5 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties
      Removed value: -{
      -  "cart_id": {
      -    "description": "Cart session ID returned by create_cart",
      -    "type": "string"
      -  },
      -  "shipping_address": {
      -    "additionalProperties": false,
      -    "description": "Destination address. Omit to collect via elicitation (Claude.ai).",
      -    "properties": {
      -      "address1": {
      -        "description": "Street address",
      -        "type": "string"
      -      },
      -      "city": {
      -        "description": "City",
      -        "type": "string"
      -      },
      -      "country_code": {
      -        "description": "ISO country code (e.g. US, CA)",
      -        "type": "string"
      -      },
      -      "province_code": {
      -        "description": "Province or state code (optional)",
      -        "type": "string"
      -      },
      -      "zip": {
      -        "description": "Postal / ZIP code",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "address1",
      -      "city",
      -      "country_code",
      -      "zip"
      -    ],
      -    "type": "object"
      -  }
      -}
    • removedInput schema / required
      Removed value: -[
      -  "cart_id"
      -]
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "address_city": {
      -      "type": "string"
      -    },
      -    "address_country": {
      -      "type": "string"
      -    },
      -    "cart_id": {
      -      "type": "string"
      -    },
      -    "rates": {
      -      "items": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "currency": {
      -            "type": "string"
      -          },
      -          "estimated_delivery": {
      -            "type": "string"
      -          },
      -          "handle": {
      -            "type": "string"
      -          },
      -          "price": {
      -            "type": "number"
      -          },
      -          "title": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "handle",
      -          "title",
      -          "price",
      -          "currency"
      -        ],
      -        "type": "object"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "cart_id",
      -    "rates"
      -  ],
      -  "type": "object"
      -}New value: +null
  7. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing mandatory payment mandate requirements, denied-outright conditions on currency mismatch, max_amount_cents enforcement, optional token behavior, credential prerequisites, address elicitation, and the fact that there is no human login. These are exactly the operational behaviors an agent needs to know and are absent from the annotations.

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?

The description is long but well-structured with labeled sections for token, payment mandate, and credential. It is front-loaded with the core purpose, and each section earns its place given the integration complexity, though some redundancy with schema descriptions could be trimmed.

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

Completeness5/5

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

For a tool with authentication, payment mandate, and credential prerequisites, the description is remarkably complete: it covers required headers, argument alternatives, failure conditions, prerequisite tool calls, and the no-human-login rule. An output schema exists, so the lack of return-format detail is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema description coverage is 100%, the description adds meaningful parameter-level meaning: payment_mandate may be sent as an argument or X-Payment-Mandate header, its currency must match the cart or the call is denied, and its cap is enforced against the cart total. It also clarifies that agent_key can be passed as an argument or Bearer header and that create_sandbox_key must be called first.

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?

The opening sentence, 'Get available shipping rates for the cart,' names a specific verb and resource, and clearly distinguishes this from siblings like select_shipping_option and preview_checkout. The additional note about address elicitation further sharpens the tool's role.

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 description gives clear prerequisite guidance — call create_sandbox_key first, provide a payment mandate, optionally include a skyfire token — but it does not explicitly say when to use this tool versus siblings such as select_shipping_option or preview_checkout. Usage is implied by the purpose statement rather than explicitly contrasted with alternatives.

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