Skip to main content
Glama

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), DC_CLUB (Dry Cleaning), ALL_IN (Wash & Fold + Dry Cleaning), each MONTHLY or ANNUAL; current monthly prices are in get_pricing → membership. Annual billing: 1 month free (pay for 11 months, i.e. 11 × the monthly price). 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, look up the price with get_pricing and 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.

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": {
      "recentOrderCode": "<recentOrderCode>",
      "plan": "<plan>",
      "billingInterval": "<billingInterval>"
    },
    "name": "enroll_in_club"
  }
}

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.9/5.0
Behavior5/5

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

The annotations mark this as a non-read-only, non-idempotent, destructive, open-world operation, and the description supplies the critical consequences: the card is charged immediately, the plan renews automatically, and cancellation stops future renewals but gives no refund for unused time. It also discloses the saved-card failure path and promo-code rejection on ANNUAL, which are important behaviors beyond the annotations.

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 description is front-loaded with purpose and prerequisites, and nearly every sentence carries operational value for a financially destructive subscription action. It is dense and somewhat long for a single paragraph, so structuring the pricing, consent, and cancellation details separately would improve scanability, but there is little wasted wording.

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 destructive subscription tool with five parameters and no output schema, the description covers the identity check, card prerequisite, plan and interval meanings, pricing lookup, consent requirements, billing timing, renewal, cancellation, and promo restrictions. That is sufficient for an agent to call the tool safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is already 100%, but the description adds meaning beyond the schema: it maps WF_CLUB, DC_CLUB, and ALL_IN to their service coverage, explains that ANNUAL billing means paying for 11 months, and clarifies that WELCOME gives the first month free only on MONTHLY billing. It also reinforces that recentOrderCode and email function as an identity pair.

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 states a specific action and resource: enroll a Fold customer in Fold Club. It clearly distinguishes the tool from pricing lookup (get_pricing) and order tracking (track_order), and it names the available plans and billing intervals so the agent knows exactly what the tool does.

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?

It gives explicit prerequisites: a recent order code plus matching email, and a saved card on file. It also prescribes the pre-call workflow — look up the price with get_pricing, tell the customer the exact amount, renewal terms, and cancellation method, and obtain explicit consent — and it constrains promo code use to MONTHLY billing.

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