Skip to main content
Glama

iMoving - moving quotes

Get moving prices

get_moving_quote
Read-onlyIdempotent

Gets real prices from vetted movers for a home move within the United States: how many movers can do it, the price range, and the best offers (the cheapest, plus the top-rated mover) with rating, reviews, price and a booking_url. Nothing is booked or stored.

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_size_id": "<move_size_id>",
      "move_date": "<move_date>"
    },
    "name": "get_moving_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the cheapest offers to return, 1-10. Default 5.
to_zipYes5-digit US ZIP code of the destination, e.g. "10001".
from_zipYes5-digit US ZIP code of the place being moved out of, e.g. "33101".
move_dateYesMoving day as YYYY-MM-DD, from tomorrow up to 18 months ahead.
move_size_idYesThe id of the home size, from list_move_sizes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that the operation is read-only, idempotent, closed-world, and non-destructive. The description adds meaningful behavioral context by saying nothing is booked or stored and by describing the returned quote components, including ratings, reviews, price, and booking_url. It stops short of covering freshness, availability constraints, or rate limits.

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 compact, front-loaded with the core action, and then lists the key outputs without filler. Every clause contributes useful information for an agent deciding whether and how to call the 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?

There is no output schema, but the description enumerates what a quote returns: mover count, price range, and best offers with their attributes. Combined with fully documented input parameters and annotations covering safety and idempotency, the definition is complete enough for an agent to invoke it correctly.

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 input schema already explains the ZIP codes, move date, move size id, and limit. The description does not add parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: it gets real prices from vetted movers for a US home move, and it names the outputs such as mover count, price range, and best offers. That makes the tool's purpose clear, though it does not explicitly distinguish itself from the sibling tools get_mover or list_move_sizes.

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 "for a home move within the United States" and by the note that nothing is booked or stored, which signals that this is a pricing step rather than a booking or mover-detail step. However, the description never names alternatives or says when to use this instead of get_mover or list_move_sizes.

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