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

AQX Logistics Shipping Rates & Tracking MCP Server

Official

check_us_store_forwarding

Check if a US retailer accepts international cards and ships to freight forwarders, or requires AQX Buy For Me concierge service before ordering.

Instructions

Check whether a major US retailer accepts international cards and ships to freight forwarders, or requires AQX Buy For Me concierge.

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": {
      "store_name": "<store_name>"
    },
    "name": "check_us_store_forwarding"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 burden. It implies a read-only eligibility check but says nothing about whether the lookup is live or cached, whether auth or a configured integration is required, or what the response looks like (boolean, enum, or multi-field verdict), leaving the agent to guess the tool's behavior.

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 no filler; the compound criteria are dense but each clause carries real information. Slightly hard to parse due to the trailing 'or requires AQX Buy For Me concierge' clause.

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?

The description covers what is evaluated, which is the core need for a one-parameter check tool with no output schema. It is still incomplete on input format and result shape, both of which an agent needs in order to call and interpret it confidently.

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 coverage is 0% for the single store_name parameter, and the description never mentions it, so neither source says whether it expects a store name, domain, or internal ID. The description adds no meaning beyond the schema's bare string field.

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?

States a specific check with concrete criteria: international card acceptance, freight-forwarder shipping, and whether AQX Buy For Me concierge is required. It is clearly a different operation from calculate_shipping_rate and track_aqx_shipment, though it does not explicitly name or contrast those siblings.

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?

Usage is implied by the criteria being checked: an agent would call it when qualifying a US retailer for an international purchase. There is no explicit when-to-use trigger, no prerequisites, and no guidance on what to do with each possible outcome.

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