Skip to main content
Glama

Moving quote (paid, $0.01)

get_quote

Paid version of get_quote_free: the same indicative price from the same inputs, for $0.01 per call via x402 (USDC on Base, eip155:8453). Prefer get_quote_free, which is free and also returns booking details. Use this tool only when get_quote_free returns its rate-limit error (30 free quotes per hour per IP) or your agent is set up to pay per call. It has no contact fields and never creates a lead; to reach the movers use get_quote_free with contact details, or request_booking. Required: from_zip, to_zip, move_date (e.g. "20850", "60601", "2026-11-14"); size the move with cubic_feet, inventory, home_size or bedrooms. Input is checked before payment and invalid input is not charged. The first call returns an x402 payment requirement; retry with the payment in _meta["x402/payment"]. Returns quote_id, move_type (long_distance, local, or local_not_offered for short moves outside DC/MD/VA), indicative_total in USD, a line-item breakdown and the survey handoff. Indicative price per tariff, not a legal estimate.

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": {
      "from_zip": "<from_zip>",
      "to_zip": "<to_zip>",
      "move_date": "<move_date>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
safesNoNumber of safes, $500 each
to_zipYesDelivery 5-digit US ZIP in any US state, e.g. "32801". Over about 50 road miles is priced as long distance per cubic foot; shorter moves are priced hourly only when both ZIPs are in DC/MD/VA
packingNo"full" adds full packing at $1.25 per cf (long distance); "none" or omitted means no packing. Partial packing is priced at the survey
shuttleNoShuttle truck needed, $1.25 per cf, $700 minimum
bedroomsNoNumber of bedrooms (0-10), e.g. 2; use instead of home_size
from_zipYesPickup 5-digit US ZIP, e.g. "20850"
crew_sizeNoLocal only: 2 movers $229/hr, 3 movers $259/hr, 4 movers $299/hr
est_hoursNoLocal only: estimated labor hours (3-hour minimum)
home_sizeNoHome size: studio, 1br, 2br, 3br, 4br or 5br+. The easiest way to size the move; used to estimate cubic feet (long distance) or crew and hours (local). Ignored for long distance when cubic_feet or a sized inventory is given
inventoryNoOptional item list, e.g. [{"name":"sofa","quantity":1,"cubic_feet":50}]. Give cubic_feet or weight_lbs per item (weight converted at 6.5 lb/cf); used instead of home_size when at least one item has a size
move_dateYesEarliest pickup date, YYYY-MM-DD, e.g. "2026-11-14"
unpackingNoFull unpacking at $1.25 per cf (long distance)
cubic_feetNoTotal shipment cubic feet if known, e.g. 900. Takes priority over inventory, home_size and bedrooms for long distance (350 cf minimum billed)
extra_stopsNoExtra pickup or delivery stops, $150 each
stairs_flightsNoFlights of stairs, $75 per flight
storage_monthsNoMonths of storage, $50 per 100 cf per month
long_carry_feetNoLong carry distance in feet, $100 per 75 ft
specialty_itemsNoBulky items with a flat handling fee, e.g. ["piano_upright"]. Allowed: piano_upright, piano_grand, piano_baby_grand, motorcycle, atv, pool_table, jacuzzi, appliance, aquarium, misc_bulky
guaranteed_deliveryNoGuaranteed delivery date, 42% of line haul (long distance)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / properties / bedrooms / description
      Previous value: -"Alternative to home_size"New value: +"Number of bedrooms (0-10), e.g. 2; use instead of home_size"
    • changedInput schema / properties / cubic_feet / description
      Previous value: -"Total shipment cubic feet, if known (350 cf minimum applies)"New value: +"Total shipment cubic feet if known, e.g. 900. Takes priority over inventory, home_size and bedrooms for long distance (350 cf minimum billed)"
    • changedInput schema / properties / from_zip / description
      Previous value: -"Origin 5-digit US ZIP"New value: +"Pickup 5-digit US ZIP, e.g. \"20850\""
    • changedInput schema / properties / home_size / description
      Previous value: -"Home size; used to estimate cubic feet (long distance) or crew and hours (local)"New value: +"Home size: studio, 1br, 2br, 3br, 4br or 5br+. The easiest way to size the move; used to estimate cubic feet (long distance) or crew and hours (local). Ignored for long distance when cubic_feet or a sized inventory is given"
    • changedInput schema / properties / inventory / description
      Previous value: -"Optional item list; cubic_feet (or weight_lbs, converted at 6.5 lb/cf) per item"New value: +"Optional item list, e.g. [{\"name\":\"sofa\",\"quantity\":1,\"cubic_feet\":50}]. Give cubic_feet or weight_lbs per item (weight converted at 6.5 lb/cf); used instead of home_size when at least one item has a size"
    • addedInput schema / properties / inventory / items / properties / cubic_feet / description
      Added value: +"Size of one item in cubic feet"
    • addedInput schema / properties / inventory / items / properties / name / description
      Added value: +"Item name, e.g. \"sofa\""
    • addedInput schema / properties / inventory / items / properties / quantity / description
      Added value: +"How many of this item (default 1)"
    • addedInput schema / properties / inventory / items / properties / weight_lbs / description
      Added value: +"Weight of one item in pounds"
    • changedInput schema / properties / move_date / description
      Previous value: -"Earliest pickup date, YYYY-MM-DD"New value: +"Earliest pickup date, YYYY-MM-DD, e.g. \"2026-11-14\""
    • changedInput schema / properties / packing / description
      Previous value: -"Full packing at $1.25 per cf (long distance)"New value: +"\"full\" adds full packing at $1.25 per cf (long distance); \"none\" or omitted means no packing. Partial packing is priced at the survey"
    • changedInput schema / properties / specialty_items / description
      Previous value: -"Bulky items with a tariff handling charge"New value: +"Bulky items with a flat handling fee, e.g. [\"piano_upright\"]. Allowed: piano_upright, piano_grand, piano_baby_grand, motorcycle, atv, pool_table, jacuzzi, appliance, aquarium, misc_bulky"
    • changedInput schema / properties / to_zip / description
      Previous value: -"Destination 5-digit US ZIP, any US state. Over about 50 road miles is priced as long distance per cubic foot; shorter moves are priced hourly only within DC/MD/VA"New value: +"Delivery 5-digit US ZIP in any US state, e.g. \"32801\". Over about 50 road miles is priced as long distance per cubic foot; shorter moves are priced hourly only when both ZIPs are in DC/MD/VA"
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so well: it discloses the $0.01 x402 payment flow, USDC on Base, the first-call payment requirement and retry mechanism, pre-payment input validation, the 30-free-quotes-per-hour rate limit context, and that no lead is created. It also lists return fields and the tariff disclaimer, which are important behavioral and output expectations.

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?

The description is long but dense and front-loaded: it immediately establishes paid vs free status and the primary usage rule, then covers payment mechanics, required inputs, return values, and disclaimers. Every sentence contributes useful context for a 19-parameter paid tool.

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?

The description is complete for this tool: it explains the payment workflow, rate-limit trigger, required inputs, return fields, and legal disclaimer, even though no output schema or annotations exist. An agent has enough information to decide whether to call it and how to handle the x402 retry.

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 description coverage is 100%, so the schema already documents all 19 parameters thoroughly. The description reinforces the required fields and sizing options but largely mirrors what the schema says rather than adding new parameter meaning, so the baseline 3 is appropriate.

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 description states a specific verb and resource: a paid moving quote via get_quote, explicitly framed as the paid counterpart to get_quote_free. It distinguishes itself from siblings by saying it has no contact fields, never creates a lead, and that booking/contact use cases belong to get_quote_free or request_booking.

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?

It gives explicit when-to-use guidance: prefer get_quote_free, and use this tool only when get_quote_free returns its rate-limit error or when the agent is set up to pay per call. It also names alternatives for contacting movers and booking, leaving little inference needed.

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