Skip to main content
Glama

Get referral code

get_referral_code
Read-onlyIdempotent

Look up a customer's Fold referral code and share link. Use this when the customer wants to share Fold with a friend or check how many people they've successfully referred. Returns the code, a ready-to-paste link (foldlaundry.com/r/CODE), and stats. Both sides get referral credit (amount in the reward field of the response) after the friend completes their first pickup.

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": {
      "email": "<email>"
    },
    "name": "get_referral_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesCustomer email used at Fold signup. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 this as a safe, idempotent, closed-world read, so the bar is lower, yet the description still adds real behavior: what the response contains, the link format, where the credit amount lives (reward field), and the business condition that credit lands after the friend's first pickup. It doesn't note any auth or privacy consideration for looking up a customer by email, which is the one remaining behavioral gap.

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?

Four sentences, front-loaded with the action and followed by trigger conditions and return shape. The referral-credit sentence is somewhat ancillary but still earns its place by explaining the reward field.

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?

There is no output schema, and the description compensates by naming the returned code, link, stats, and reward field, which is enough for an agent to use the result. Nothing is said about whether a missing email yields an error versus creating a code, a minor gap for a single-parameter lookup.

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?

With one parameter at 100% schema coverage, the schema already carries the semantics of email, and the description adds only the framing that it identifies "a customer's" code. Baseline 3 applies since nothing meaningful about the parameter is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Look up a customer's Fold referral code and share link" states a specific verb (look up) and specific resources (referral code, share link), which is clearly distinct from the order/hotel/account siblings. It stops short of naming a related sibling such as apply_promo_code to draw the line explicitly.

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?

It gives concrete when-to-use triggers: the customer wants to share Fold with a friend, or wants to check how many people they've referred. No when-not guidance or named alternative is offered, so the agent must infer that applying someone else's code is a different tool.

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