Skip to main content
Glama

Fold Laundry

by com.foldlaundry
OverviewDiscussionsAdmin

Enroll in Fold Club

enroll_in_club
Destructive

Enroll a Fold customer in Fold Club. Requires a recent order code + email for identity (same auth model as track_order). The customer MUST have a saved card on file — if not, we return an error pointing them to /app/payment. Three plans: WF_CLUB (Wash & Fold $19.99/mo or $219.89/yr), DC_CLUB (Dry Cleaning $12.99/mo or $142.89/yr), ALL_IN (Wash & Fold + Dry Cleaning $29.99/mo or $329.89/yr). Annual billing: 1 month free (pay for 11 months). The card is charged immediately and the plan renews automatically (every month, or every year for ANNUAL) at that price until cancelled; cancel any time in the app (Account → Fold Club) — the plan then runs to the end of the paid month/year with no refund for unused time. Before calling this tool, tell the customer the exact amount, that it renews automatically, and how to cancel, and get their explicit yes. promoCode WELCOME gives the first month free on MONTHLY billing only (it is typically sent to customers by SMS/email after their first delivery); promo codes are rejected on ANNUAL.

Input Schema

NameRequiredDescriptionDefault
planYesWhich Club plan to enroll in.
emailNoCustomer email — must match the recentOrderCode owner.
promoCodeNoOptional Stripe promo code (e.g. WELCOME for first month free). MONTHLY billing only.
billingIntervalYesBilling cadence. ANNUAL: 1 month free (pay for 11 months), charged once per year in advance, renews automatically each year.
recentOrderCodeYesA recent Fold order code (FOLD-XXXXX) belonging to this customer — used as proof of identity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / billingInterval / description
      Previous value: -"Billing cadence. ANNUAL saves ~2 months vs monthly."New value: +"Billing cadence. ANNUAL: 1 month free (pay for 11 months), charged once per year in advance, renews automatically each year."
    • changedInput schema / properties / promoCode / description
      Previous value: -"Optional Stripe promo code (e.g. WELCOME for first month free)."New value: +"Optional Stripe promo code (e.g. WELCOME for first month free). MONTHLY billing only."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive/openWorld/non-idempotent) by disclosing that the card is charged immediately, the plan auto-renews, cancellation runs to period end with no refund, and the specific failure mode when no card is on file. This is exactly the behavioral context a billing mutation tool needs.

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-loads purpose then layers prerequisites, pricing, billing/renewal terms, and pre-call instructions. Dense and every sentence is load-bearing, though the three-plan pricing would scan better as a list and the paragraph is long.

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 5-param billing mutation with no output schema and rich annotations, the description covers prerequisites, charge/renewal behavior, cancellation, promo rules, and the error return path. An agent has everything needed to call it correctly and safely.

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 meaning the schema lacks: exact per-plan pricing, the annual '1 month free' framing, and promoCode constraints (WELCOME is MONTHLY-only and rejected on ANNUAL). It notably omits that email is optional/conditional in the schema versus its stated identity role.

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: 'Enroll a Fold customer in Fold Club.' It clearly distinguishes itself from sibling enrollment/purchase tools like activate_semester_pass or subscribe_order_updates by naming the Fold Club product and its three plan codes.

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 strong preconditions (recent order code + email identity, saved card required, error path to /app/payment) and an explicit pre-call obligation to confirm charge, auto-renewal, cancellation, and obtain consent. It stops short of naming when-not-to-use or alternative tools beyond the track_order auth-model reference.

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