Skip to main content
Glama

Schedule residential pickup

book_residential_pickup
Destructive

Schedule a laundry pickup at a residential address. For any non-hotel address in the service area, including Airbnb and other vacation rentals (the rental address is the pickup address). Creates a guest customer account (no password needed — they can claim it later by signing up with the same email). Returns an order code (FOLD-XXXXX) and a Stripe payment-setup URL. The card is NOT charged until after intake. The order minimum applies (get_pricing). Only ZIPs served by Fold are accepted (see check_service_zip).

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "email": "<email>",
      "phone": "<phone>",
      "line1": "<line1>",
      "city": "<city>",
      "state": "<state>",
      "zipCode": "<zipCode>",
      "services": "<services>",
      "pickupDate": "<pickupDate>",
      "pickupWindow": "<pickupWindow>"
    },
    "name": "book_residential_pickup"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity, e.g. "Los Angeles"
emailYesCustomer email (used for tracking + receipts)
line1YesStreet address line 1, e.g. "123 Main St"
line2NoApartment / suite / unit (optional)
notesNoOptional special instructions about the laundry (e.g. "no fabric softener").
phoneYesCustomer mobile: US 10-digit, or E.164 with country code (+1…, +44…) for international guests
stateYesUS state code, e.g. "CA"
zipCodeYes5-digit ZIP. Must be in service area (use check_service_zip first).
lastNameYesCustomer last name
servicesYesWhat services to perform.
firstNameYesCustomer first name
pickupDateYesYYYY-MM-DD date for pickup. Must be today or in the future.
deliveryDateNoYYYY-MM-DD delivery date. Defaults to pickup date + 1 day if omitted.
pickupWindowYesPickup time window label from check_service_zip.pickupWindows, e.g. "9-11 AM".
deliveryNotesNoHow to find / deliver to the address (gate code, doorman, leave at door, etc.).
deliveryWindowNoDelivery time window label from check_service_zip.deliveryWindows. EVENING ONLY — Fold does not deliver in the morning. Defaults to the evening window if omitted.
idempotencyKeyNoOPTIONAL — pass a unique identifier (UUID recommended) to make this call safe to retry. If we have already seen this key, we return the EXISTING order code instead of creating a duplicate. Highly recommended for production agents that may retry on network errors.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / phone / description
      Previous value: -"Customer phone in E.164 format (+1XXXXXXXXXX) or US 10-digit"New value: +"Customer mobile: US 10-digit, or E.164 with country code (+1…, +44…) for international guests"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the side effects: a guest customer account is created with no password and is claimable later, the call returns an order code (FOLD-XXXXX) and a Stripe setup URL, and the card is not charged until after intake. The only minor tension is that annotations declare idempotentHint=false while the description explains a retry-safe idempotencyKey opt-in — that is a nuance about opt-in behavior, not a contradiction, since the tool is not inherently idempotent. It stops short of describing what happens on partial failure or how the account email collides with an existing account.

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 the core action and address scope, then layers prerequisites, side effects, and return values in descending priority. Dense but nearly every sentence carries distinct information; the heavy use of parentheticals makes it slightly harder to scan than it could be.

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 17-parameter mutation with no output schema, the description supplies the missing pieces an agent needs: what gets created (guest account), what is returned (order code plus Stripe setup URL), when payment occurs, and which prerequisite tools gate a successful call. Nothing essential for a correct first invocation is absent.

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 already 100%, so the schema carries the parameter burden, including the evening-only deliveryWindow note and the idempotencyKey retry contract. The description adds only marginal param context, reinforcing the ZIP service-area constraint and pointing pickupWindow at check_service_zip.pickupWindows, which the schema itself already references. 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?

Opens with a specific verb+resource ("Schedule a laundry pickup at a residential address") and immediately scopes it against the sibling book_hotel_pickup by declaring it is for "any non-hotel address in the service area." An agent can route between residential and hotel booking without opening either 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?

Explicitly states when to use it (non-hotel addresses, including Airbnb and vacation rentals, with the rental address as pickup address) and names the prerequisite tools by name — get_pricing for the order minimum and check_service_zip for served ZIPs. Both inclusion and the gating conditions are spelled out.

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