Skip to main content
Glama

Join the waitlist

join_waitlist
Idempotent

Adds an email address to Fold's waitlist for a ZIP code Fold doesn't serve yet; Fold emails if service starts there. Only for unserved ZIPs (served ZIPs return an error saying Fold already serves them). Use the person's own email with their permission.

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>",
      "zipCode": "<zipCode>"
    },
    "name": "join_waitlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe person's email address.
zipCodeYes5-digit US ZIP code where they want service.
firstNameNoOptional first name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world behavior; the description adds value beyond them by disclosing the error path for served ZIPs and the downstream effect (Fold emails when service starts). It does not describe the return payload or any duplicate-signup behavior, but the safety profile is well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two front-loaded sentences with no filler: the action and scope come first, then the exclusion and consent caveat. Every clause carries information an agent would otherwise have to guess.

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 three-parameter write with no output schema, the description covers purpose, preconditions, failure behavior, and the follow-up email, which is everything needed to call it correctly. Nothing material is left implicit.

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 still adds semantics by constraining zipCode to unserved areas and framing email as the end user's own address with permission. Those are real constraints not encoded in the schema.

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+resource (adds an email to the waitlist) scoped to ZIP codes Fold doesn't serve, which cleanly separates it from the sibling check_service_zip and from enrollment/booking tools. An agent knows exactly what this tool creates without opening the schema.

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 an explicit precondition ('Only for unserved ZIPs') and states the failure mode for served ZIPs, plus a consent rule ('Use the person's own email with their permission'). It stops short of naming check_service_zip as the preferred way to verify coverage first, so the routing is implied rather than spelled out.

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