Cross Country Movers Quote

Get international moving quote

get_international_quote

Read-onlyIdempotent

Use this tool when a user wants to estimate the cost of an international household move from the USA to another country, or from another country to the USA, with Cross Country Movers: overseas moving, shipping household goods abroad, container moving. Inputs: origin and destination (US city + state, or city + country), home size (studio, 1-4 bedrooms) or cubic feet, optional first available date. Returns an estimated price range (low end first) for that country and home size, or a callback offer when a route needs a specialist. Customs, duties and destination fees are not included. Estimates only, not binding; nothing is booked. Do not use for moves within the US (use get_long_distance_quote) or for shipping only a car.

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "get_international_quote"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No
`origin`	Yes
`cubic_feet`	No
`destination`	Yes
`first_available_date`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial context beyond the annotations (which only declare read-only/idempotent safety): estimates are non-binding, nothing is booked, customs/duties/destination fees are excluded, and a callback may be offered instead of a price. These are exactly the behavioral facts an agent needs before presenting a number to a user.

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?

Front-loads the trigger condition, then inputs, then return shape, then exclusions — a logical order with no filler. The keyword-stuffed opening sentence ('overseas moving, shipping household goods abroad, container moving') is slightly redundant padding that a tighter version could drop.

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?

Covers trigger, inputs, return shape, pricing caveats, and exclusions, and the output schema means return values need not be fully spelled out. The only remaining gap is disambiguating size versus cubic_feet, and no note on accuracy or latency of estimates beyond 'estimates only'.

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

Parameters4/5

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

With 0% schema description coverage, the description carries the burden and mostly succeeds: it defines origin/destination formats (US city+state, or city+country), the size enum values (studio, 1-4 bedrooms), the cubic-feet alternative, and that the date is optional and means 'first available'. It does not clarify how size and cubic_feet interact when both are supplied, nor any expected value range for cubic_feet.

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 ('estimate the cost of an international household move') plus explicit scope (USA<->another country, household goods, container moving, provided by Cross Country Movers). It is immediately distinguishable from the domestic sibling, which it names.

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 explicit when-to-use ('user wants to estimate the cost of an international move'), explicit when-not-to-use ('Do not use for moves within the US... or for shipping only a car'), and names the correct alternative tool get_long_distance_quote. It also flags the callback path for specialist routes.

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

All Cross Country Movers Quote tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?