Skip to main content
Glama

Fold Laundry

by com.foldlaundry
OverviewDiscussionsAdmin

Get estimate

get_estimate
Read-onlyIdempotent

Calculate an itemized price estimate for what the user actually wants — bags or pounds of wash & fold plus dry-cleaning garments named in plain words (e.g. '2-piece suit', 'dress shirt', 'winter coat'). Answers 'how much will it cost' before scheduling. Returns line items, subtotal, and total in cents and USD (no hidden fees; orders under the $39.99 minimum are billed at the minimum). Note: the actual charge is calculated at intake when bags are weighed, but this estimate is accurate to within ~10% for typical orders. These are residential prices — hotel guest orders are priced differently (see get_pricing hotelGuestRates).

Input Schema

NameRequiredDescriptionDefault
zipCodeNoOptional ZIP for market-specific pricing (defaults to LA rates if omitted).
washFoldBagsNoNumber of W&F bags. Each bag holds ~22 lb. Set to 0 if no W&F.
washFoldPoundsNoAlternative to washFoldBags — total pounds for à-la-carte PAYG W&F pricing ($2.65/lb). Use one or the other, not both.
dryCleaningItemsNoDry-cleaning garments. Name each one in plain words; it is matched to Fold's garment list: Dress shirt, Blouse, Polo shirt, T-shirt, Tank top / cami, Scarf, Tie, Pants / slacks, Jeans, Skirt, Shorts, Sweater, Cardigan, Vest, Light jacket, Dress, Jumpsuit / romper, Blazer, Sport coat, Light coat / trench, Suit jacket (1 piece), 2-piece suit, 3-piece suit, Gown / formal dress, Tuxedo, Winter coat / parka, Leather jacket (light). Unrecognized names are returned in unmatchedItems instead of being priced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / dryCleaningItems / description
      Previous value: -"List of dry-cleaning items, each with a tier. Tiers: T1 (basic shirts $4.50), T2 (dress shirts $6), T3 (pants/skirts $9), T4 (dresses/sweaters $12), T5 (jackets/coats $15), T6 (gowns/suits $19.50)."New value: +"Dry-cleaning garments. Name each one in plain words; it is matched to Fold's garment list: Dress shirt, Blouse, Polo shirt, T-shirt, Tank top / cami, Scarf, Tie, Pants / slacks, Jeans, Skirt, Shorts, Sweater, Cardigan, Vest, Light jacket, Dress, Jumpsuit / romper, Blazer, Sport coat, Light coat / trench, Suit jacket (1 piece), 2-piece suit, 3-piece suit, Gown / formal dress, Tuxedo, Winter coat / parka, Leather jacket (light). Unrecognized names are returned in unmatchedItems instead of being priced."
    • addedInput schema / properties / dryCleaningItems / items / properties / garment
      Added value: +{
+  "description": "Garment in plain words, e.g. 'suit', 'blouse', 'parka'.",
+  "type": "string"
+}
    • changedInput schema / properties / dryCleaningItems / items / properties / hangDry / description
      Previous value: -"Add $2 hang-dry fee per garment."New value: +"Hang-dry instead of folding."
    • addedInput schema / properties / dryCleaningItems / items / properties / tier / description
      Added value: +"Deprecated — use garment."
    • changedInput schema / properties / dryCleaningItems / items / required
      Previous value: -[
-  "tier",
-  "quantity"
-]New value: +[
+  "quantity"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark this read-only and idempotent, yet the description still adds real behavior: no hidden fees, the $39.99 minimum billing floor, ~10% accuracy versus the intake weight charge, and that unrecognized garment names are returned in unmatchedItems rather than priced. These are exactly the caveats an agent needs to set expectations when quoting a price.

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 progressively adds constraints, minimum, accuracy caveat, and the residential/hotel distinction — a logical order with little waste. It runs long for a single paragraph and repeats the residential-pricing point in a way that could be tightened.

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?

With no output schema, the description carries the return shape itself (line items, subtotal, total in cents and USD) and covers the minimum-charge and accuracy edge cases. Nothing material is missing for an agent 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 baseline is 3; the description earns a step up by framing the two input modes (bags vs. pounds of wash & fold) and by supplying concrete garment phrasing examples like '2-piece suit'. It doesn't restate the 10-bag/200-lb caps or the deprecated tier field, but the schema covers those.

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?

The description opens with a specific verb and resource — 'Calculate an itemized price estimate' — and immediately scopes it to wash & fold bags/pounds plus plain-word dry-cleaning garments. That framing separates it from get_pricing (rate lookup) and the book_* siblings (scheduling) without any schema inspection.

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?

'Answers how much will it cost before scheduling' states the trigger condition explicitly, and the closing sentence routes hotel guest orders elsewhere ('see get_pricing hotelGuestRates'), so the exclusions and the alternative are both named.

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