Skip to main content
Glama
AQX Logistics Shipping Rates & Tracking MCP Server

AQX Logistics Shipping Rates & Tracking MCP Server

Official

calculate_shipping_rate

Calculate live AQX Logistics air freight costs from the USA to 15 destination countries using actual or dimensional weight so you can estimate landed shipping rates before booking.

Instructions

Calculate live AQX Logistics air freight cost from USA (LAX hub: 309 E Arbor Vitae St, Inglewood, CA 90301) to 15 destination countries.

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>",
      "actual_weight_kg": "<actual_weight_kg>"
    },
    "name": "calculate_shipping_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
width_cmNo
height_cmNo
length_cmNo
actual_weight_kgYes
destination_countryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and mostly does not: it does not say whether an external carrier API is called, whether the returned cost is a single figure or a range, which currency it is in, or whether any fees/surcharges are included. 'Live' is the only behavioral signal, implying rates are fetched rather than cached, which is useful but thin.

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?

A single front-loaded sentence with the key scope facts (origin hub, destination count) and no filler. It is efficient, though it spends words on a street address that the agent is unlikely to need for invocation.

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

Completeness2/5

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

Five parameters, no annotations, no output schema, and 0% schema coverage is a demanding profile, and the one-sentence description does not cover the allowed destination list, dimension/volumetric-weight behavior, or the shape and currency of the returned cost. An agent could form a call, but with several guesses.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and largely does not. '15 destination countries' hints that destination_country is constrained to a fixed set, but the description never enumerates it, and it says nothing about actual_weight_kg units, the optional length/width/height defaults of 0, or whether dimensions trigger volumetric-weight pricing.

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 gives a specific verb+resource ('Calculate live AQX Logistics air freight cost') plus origin (LAX hub address) and scope (15 destination countries), so an agent knows exactly what it does. It does not name or distinguish itself from the siblings (track_aqx_shipment, check_us_store_forwarding), though their purposes are visibly different.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of when a quote should be refreshed versus reused. The word 'live' hints at real-time quoting, but the agent is left to infer the workflow context entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.