Skip to main content
Glama

Reschedule order

reschedule_order
DestructiveIdempotent

Move the pickup date/window, delivery date/window, or both, on an existing order. Pickup can only be moved while still in SCHEDULED or PICKUP_ASSIGNED (i.e. driver has not started). Delivery can be moved any time before the delivery driver is en route. Requires order code + email. Pass at least one leg.

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": {
      "orderCode": "<orderCode>"
    },
    "name": "reschedule_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail used when scheduling. Not needed when the customer has connected their Fold account.
orderCodeYesOrder code (FHL-XXXXXX or FOLD-XXXXX).
newPickupDateNoYYYY-MM-DD — new pickup calendar date.
newDeliveryDateNoYYYY-MM-DD — new delivery calendar date.
newPickupWindowNoPickup window label, e.g. "9-11 AM".
newDeliveryWindowNoDelivery window label from check_service_zip.deliveryWindows (evening only, e.g. "6:30 PM – 9:30 PM").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Email used at booking. Not needed when the customer has connected their Fold account."New value: +"Email used when scheduling. Not needed when the customer has connected their Fold account."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description adds valuable state gating and the driver-en-route cutoff. However, it never explains why the operation is destructive — whether the original slot/assignment is released or lost, whether fees apply, or what a failure looks like. It also says 'Requires order code + email' while the schema marks email conditionally unnecessary for Fold-connected customers, a small inaccuracy.

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?

Four short sentences, front-loaded with what moves and immediately followed by the eligibility cutoffs and the minimum-argument rule. No filler and no restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, idempotent mutation with six params and no output schema, the description covers eligibility, required identifiers, and the at-least-one-leg rule. What it leaves out — the return payload, whether the prior booking is released, and any cost or cutoff edge cases — is what an agent would still need to set expectations.

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, but the description adds a cross-parameter constraint the schema does not express: at least one of the pickup/delivery legs must be supplied (schema only requires orderCode). That materially changes how an agent fills the six parameters. The email-requirement claim mildly conflicts with the schema's conditional note.

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?

States a specific verb and resource with scope: moving pickup/delivery date or window on an existing order, explicitly allowing one leg or both. It is clearly distinguishable from cancel_order or update_recurring_pickup by the 'existing order + move date/window' framing, though no sibling is named to sharpen the boundary (e.g. vs. set_recurring_pickup).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete eligibility states (pickup only in SCHEDULED or PICKUP_ASSIGNED; delivery any time before driver en route) and the 'pass at least one leg' precondition, which is genuine when-to-use guidance. It does not name alternatives such as cancel_order for orders outside those states, so an agent facing an ineligible order has no routing hint.

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