Skip to main content
Glama

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 order 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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_estimate"
  }
}

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 (per-lb rate in get_pricing). Use one or the other, not both.
dryCleaningItemsNoDry-cleaning garments. Name each one in plain words; it is matched to Fold's garment list (see get_pricing → dryCleaning). Unrecognized names are returned in unmatchedItems instead of being priced.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / dryCleaningItems / description
      Previous 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."New value: +"Dry-cleaning garments. Name each one in plain words; it is matched to Fold's garment list (see get_pricing → dryCleaning). Unrecognized names are returned in unmatchedItems instead of being priced."
    • changedInput schema / properties / washFoldPounds / description
      Previous value: -"Alternative to washFoldBags — total pounds for à-la-carte PAYG W&F pricing ($2.65/lb). Use one or the other, not both."New value: +"Alternative to washFoldBags — total pounds for à-la-carte PAYG W&F pricing (per-lb rate in get_pricing). Use one or the other, not both."
  2. 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"
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent/non-destructive annotations: it discloses the return payload (line items, subtotal, total in cents and USD), the order-minimum billing rule, the ~10% accuracy bound versus weighed intake, and the residential-vs-hotel price divergence. These are exactly the caveats an agent needs to set user expectations.

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?

The core purpose and the pre-scheduling framing are front-loaded, and the caveats (minimum, accuracy, residential pricing) are packed into trailing clauses. It is dense but nearly every clause carries information; the garment examples are the only mildly redundant part.

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 steps in to describe the return shape, currency units, and the unmatchedItems edge case, plus the pricing caveats. For a zero-required-parameter read-only estimator, nothing material is left for the agent to guess.

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 100%, so every parameter already carries its own documentation, including bag capacity, the bags-vs-pounds exclusivity, and the unmatchedItems fallback. The description adds plain-words garment naming guidance, but that largely restates the schema; a 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?

States a specific verb and resource — calculate an itemized price estimate — and immediately scopes it to wash & fold bags/pounds plus dry-cleaning garments. It distinguishes itself from get_pricing (rates) and from the booking tools by framing the job as answering 'how much will it cost' before scheduling.

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?

The phrase 'Answers how much will it cost before scheduling' clearly implies when to reach for it, and it explicitly routes hotel guest pricing elsewhere via 'see get_pricing hotelGuestRates'. It stops short of an explicit when-not/alternative statement for the residential case (e.g. 'use get_pricing to browse rates'), so it is clear context rather than full routing.

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