Skip to main content
Glama

Request a custom shipping quote (heavy/oversize, freight, customs paperwork)

request_shipment_quote

Sends a shipping request to the Global Shopaholics team for a manual quote or help with a shipment, labels or customs paperwork (e.g. heavy/oversize items, freight, multiple boxes). Nothing is charged. Call only after the user confirms details. Returns a reference id and next steps. For instant prices use get_shipping_rates instead.

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": {
      "destination_country": "<destination_country>",
      "contents": "<contents>",
      "name": "<name>",
      "email": "<email>"
    },
    "name": "request_shipment_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesCustomer full name.
emailYesCustomer email; GS replies here.
needsNo
notesNo
phoneNoOptional phone/WhatsApp with country code.
contentsYesWhat is being shipped.
packagesNoBoxes (weight + optional dimensions).
destination_cityNo
declared_value_usdNo
destination_countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=true; the description adds real context beyond them: the request is handled manually by staff, no charge is incurred, and the response is a reference id plus next steps. It does not mention that idempotentHint=false means repeated calls create duplicate tickets, which is the one behavioral gap an agent would want flagged.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action and its scope, then cost, precondition, return value and the alternative. Every sentence carries a distinct fact and none is redundant.

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 10-parameter, non-idempotent, human-in-the-loop submission tool with no output schema, the description covers purpose, cost, timing precondition, and what comes back. It is slightly thin on the parameter-level detail an agent would need to build a complete request without guessing on `needs` and `packages`.

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 only 50%, so the description should carry weight, and it partly does by naming the needs it supports ('labels', 'customs paperwork', 'freight', 'multiple boxes') which implicitly maps to the `needs` enum values. However, it never explains `notes`, `declared_value_usd`, `phone`, or `destination_city`, and adds no formatting guidance for the packages array, so half the parameters remain undocumented in both places.

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 — sends a shipping request to the Global Shopaholics team for a manual quote — and enumerates the concrete cases it covers (labels, customs paperwork, heavy/oversize items, freight, multiple boxes). It explicitly contrasts with the instant-price sibling, so an agent can separate the two without opening a schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition ('Call only after the user confirms details') and an explicit routing rule ('For instant prices use get_shipping_rates instead'). Both the when-to-use and the when-to-use-something-else conditions are stated, leaving nothing to inference.

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.