Skip to main content
Glama

Moving quote (free)

get_quote_free

Free indicative moving price from Next Generation Movers, a licensed carrier (USDOT 3764697). Use this first for any US household move quote: long distance between any two US ZIP codes, or local moves within DC/MD/VA. Use get_quote only if this tool returns its rate-limit error (30 free quotes per hour per IP) and you can pay $0.01 via x402. Use request_booking once the customer has chosen a date and wants to hold it. Use company_info for licensing or contact facts without a price. Required: from_zip, to_zip, move_date (e.g. "20850", "32801", "2026-11-14"). Size the move with cubic_feet, inventory, home_size (e.g. "2br") or bedrooms; with none of these a 2br home is assumed. Optional contact_name plus contact_phone or contact_email sends the request to the owners as a callback lead; leave them out for a price only. Returns quote_id, move_type (long_distance, local, or local_not_offered for short moves outside DC/MD/VA), indicative_total in USD with a line-item breakdown, a book object (phone (240) 422-2243, website, booking URL) and lead status. Indicative price per tariff, not a legal estimate; a free in-home or video survey comes before the written 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_free"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional details for the movers, up to 1000 characters, e.g. "3rd floor walk-up, upright piano"
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
contact_nameNoOptional customer name for the callback, e.g. "Jane Doe"
contact_emailNoOptional customer email, same purpose as contact_phone; must be a valid address
contact_phoneNoOptional customer phone. Give this or contact_email to send the quote to the owners as a callback lead; leave both out for a price only
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. Changed17 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"
    • addedInput schema / properties / contact_email / description
      Added value: +"Optional customer email, same purpose as contact_phone; must be a valid address"
    • addedInput schema / properties / contact_name / description
      Added value: +"Optional customer name for the callback, e.g. \"Jane Doe\""
    • addedInput schema / properties / contact_phone / description
      Added value: +"Optional customer phone. Give this or contact_email to send the quote to the owners as a callback lead; leave both out for a price only"
    • 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\""
    • addedInput schema / properties / notes / description
      Added value: +"Optional details for the movers, up to 1000 characters, e.g. \"3rd floor walk-up, upright piano\""
    • 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. Added

TDQS

A4.8/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden and does: it discloses the free tier and its 30/hour/IP rate limit, the paid fallback path, the coverage boundary that produces 'local_not_offered', and the side effect that supplying contact info converts a price lookup into a callback lead sent to the owners. It also flags that the price is indicative per tariff, not a legal estimate.

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 purpose, then alternatives, then required inputs, then return shape — the ordering an agent needs. It is a single dense paragraph of roughly 200 words, which makes the mid-sentence parameter rules harder to scan than a short bulleted list would.

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?

For a 23-parameter tool with no annotations and no output schema, it covers the routing decision, the required inputs with examples, the sizing fallback, the lead-vs-price branch, and the return fields (quote_id, move_type values, indicative_total with line items, book object). Nothing needed to call it correctly is missing.

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?

Schema coverage is 100%, so baseline is 3; the description earns above that by stating the unstated default ('with none of these a 2br home is assumed') and the sizing hierarchy among cubic_feet, inventory, home_size and bedrooms. It also explains the conditional semantics of contact_name plus contact_phone-or-email, which the schema only describes per-field. It does not, however, touch the many ancillary fee parameters (stairs_flights, long_carry_feet, shuttle), leaving that to the schema.

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 — 'Free indicative moving price from Next Generation Movers' — and immediately scopes the service to US household moves (long distance ZIP-to-ZIP or local within DC/MD/VA). It explicitly distinguishes itself from all three siblings by name, so an agent can route without opening any 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 default ('Use this first for any US household move quote') plus the exact condition for the alternative: 'Use get_quote only if this tool returns its rate-limit error (30 free quotes per hour per IP) and you can pay $0.01 via x402.' It also routes request_booking to the post-selection step and company_info to non-priced licensing facts. This is a complete decision tree.

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