Skip to main content
Glama

Fold Laundry

by com.foldlaundry
OverviewDiscussionsAdmin

Track order

track_order
Read-onlyIdempotent

Check the status of any Fold order — works for both hotel-guest pickups and residential pickups. Needs the order code (FOLD-XXXXXX or FHL-XXXXXX) plus the email used when scheduling; with a connected Fold account the email is not needed. Returns current state, a milestone timeline, scheduled dates, items if itemized, and proof-of-delivery photo URL if delivered.

Input Schema

NameRequiredDescriptionDefault
emailNoEmail used when scheduling. Not needed when the customer has connected their Fold account.
orderCodeNoOrder tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential). Optional when the customer has connected their Fold account: omit it to get their most recent order.

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. Changed2 schema fields changed
    • changedInput schema / properties / orderCode / description
      Previous value: -"Order tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential)"New value: +"Order tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential). Optional when the customer has connected their Fold account: omit it to get their most recent order."
    • changedInput schema / required
      Previous value: -[
-  "orderCode"
-]New value: +[]
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true and idempotent=true, so the safety profile is covered. The description goes further and enumerates what comes back (current state, milestone timeline, scheduled dates, itemized items, proof-of-delivery photo URL), which is more than the annotations provide. It does not mention what happens when an order is not found, which keeps it from a 5.

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?

Three sentences, front-loaded with the purpose before prerequisites and return contents; nothing is padding. Slightly dense in the middle sentence but still tight.

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?

With no output schema, the description compensates by describing the returned fields, and it covers the optional-parameter edge case. The main missing piece is error behavior when no matching order exists.

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 coverage is 100% and both properties already document the email-optional-when-connected rule and the FOLD-/FHL- code formats. The description largely restates that, adding the concrete 'FOLD-XXXXXX or FHL-XXXXXX' shape and 'omit it to get their most recent order', but no new semantics beyond the schema. Baseline 3 applies.

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 ('Check the status of any Fold order') and immediately scopes it as spanning both hotel-guest and residential pickups, which separates it from the booking and reschedule siblings. An agent can tell what this does without opening the schema.

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?

It gives clear prerequisites (order code + scheduling email, or neither when the Fold account is connected), which is real usage guidance. However, it never routes the agent away from plausible alternatives such as list_my_orders or subscribe_order_updates, so the when-not-to-use case is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fold Laundry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources