Skip to main content
Glama

Request a move date (free)

request_booking

Free request to hold a move date with Next Generation Movers. Use this after a quote, once the customer has chosen a date and agreed to be contacted. Do not use it to get a price (use get_quote_free). Required: move_date (YYYY-MM-DD) plus contact_email or contact_phone (requests without one are rejected). Recommended: quote_id from the quote, from_zip, to_zip, contact_name, and an idempotency_key (8-64 letters, digits or dashes, e.g. a UUID) so retries do not create duplicates. Returns hold_id, status "date_hold_pending" and next_step: the owners contact the customer within 24 hours to schedule a free in-home or video survey, then send the signed estimate and set the deposit. No payment is taken here and the date is not confirmed until then. Reusing an idempotency_key returns the existing request with duplicate: true.

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": {
      "move_date": "<move_date>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoDetails for the movers, up to 2000 characters
to_zipNoDelivery 5-digit US ZIP
from_zipNoPickup 5-digit US ZIP
quote_idNoOptional quote_id from get_quote_free or get_quote, linking the request to that quote
move_dateYesRequested move date, YYYY-MM-DD, e.g. "2026-11-14"
contact_nameNoCustomer name
contact_emailNoCustomer email. contact_email or contact_phone is required
contact_phoneNoCustomer phone. contact_email or contact_phone is required
flexible_datesNotrue if the customer can move on nearby dates
idempotency_keyNoUnique key per request, 8-64 letters, digits or dashes (a UUID works). Reusing it returns the existing request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / properties / contact_email / description
      Added value: +"Customer email. contact_email or contact_phone is required"
    • addedInput schema / properties / contact_name / description
      Added value: +"Customer name"
    • addedInput schema / properties / contact_phone / description
      Added value: +"Customer phone. contact_email or contact_phone is required"
    • addedInput schema / properties / flexible_dates / description
      Added value: +"true if the customer can move on nearby dates"
    • addedInput schema / properties / from_zip / description
      Added value: +"Pickup 5-digit US ZIP"
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Unique key per booking request (UUID recommended). Reusing it returns the same request"New value: +"Unique key per request, 8-64 letters, digits or dashes (a UUID works). Reusing it returns the existing request"
    • changedInput schema / properties / move_date / description
      Previous value: -"YYYY-MM-DD"New value: +"Requested move date, YYYY-MM-DD, e.g. \"2026-11-14\""
    • addedInput schema / properties / notes / description
      Added value: +"Details for the movers, up to 2000 characters"
    • addedInput schema / properties / quote_id / description
      Added value: +"Optional quote_id from get_quote_free or get_quote, linking the request to that quote"
    • addedInput schema / properties / to_zip / description
      Added value: +"Delivery 5-digit US ZIP"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does: no payment is taken, the date is not confirmed, owners contact the customer within 24 hours, and the follow-on sequence (survey, signed estimate, deposit) is spelled out. It also discloses the idempotency/dedup behavior ('reusing an idempotency_key returns the existing request with duplicate: true') and the rejection rule for missing contact info.

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-loaded with purpose, then usage, requirements, and return behavior in a logical order. Slightly redundant where it restates formats the schema already documents (e.g. move_date YYYY-MM-DD), but no sentence is wasted overall.

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?

No output schema exists, and the description compensates by naming the return fields (hold_id, status 'date_hold_pending', next_step) and the duplicate flag. For a 10-parameter creation tool, an agent has everything needed to call it and interpret the result.

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 the baseline would be 3, but the description adds an object-level constraint absent from the schema's required list: 'contact_email or contact_phone (requests without one are rejected)'. It also labels which fields are recommended and gives a UUID example for the idempotency key format.

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 request to hold a move date') plus the vendor, and explicitly distinguishes itself from the price-fetching sibling get_quote_free. An agent can tell this apart from get_quote/get_quote_free 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 precondition ('after a quote, once the customer has chosen a date and agreed to be contacted') and an explicit exclusion with the correct alternative ('Do not use it to get a price (use get_quote_free)'). Both when-to-use and when-not-to-use are covered.

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