Skip to main content
Glama

invite_to_coupon

Idempotent

Add email addresses to a coupon's invite list and, by default, switch the coupon to invite-only so the list is actually enforced. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees every address plus whether the coupon is about to be closed to everyone else; clients without elicitation are refused unless the deployment sets SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 and the call passes confirm_write:true (dry_run works anywhere). Addresses are lowercased and de-duplicated, malformed ones are reported rather than dropped, and an address already on the list is left exactly as it is -- so re-inviting someone who already redeemed does NOT hand them a second free account, and re-inviting someone who was revoked does NOT un-block them. Set enforce_invite_only:false only to stage a list before gating the code; the result then carries a warning that the coupon is still open. Use dry_run:true first to see exactly who would be added.

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": {
      "app_id": "<app_id>",
      "code": "<code>",
      "emails": "<emails>"
    },
    "name": "invite_to_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
app_idYes
emailsYes
sourceNo
dry_runNo
confirm_writeNo
enforce_invite_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm_write
      Added value: +{
      +  "default": false,
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes far beyond the annotations: discloses the elicitation gate, the SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES=1 escape hatch plus confirm_write:true, and that dry_run works anywhere. It also explains normalization (lowercase, de-dupe, malformed reported), the already-present-address no-op semantics with concrete consequences (no second free account, revoked stays revoked), and the warning emitted when invite-only is not enforced. This is consistent with, and much richer than, idempotentHint=true and destructiveHint=false.

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-loaded with the purpose and the default side effect, then the write gate, then data semantics, then guidance — a logical order for a dense single block. It is long and clause-heavy, but nearly every clause carries non-redundant information.

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?

No output schema exists, and the description does tell the agent what the result carries (a warning when the coupon remains open) and how to preview safely, which covers most of the risk surface for a gated write. The remaining gap is the unexplained code/app_id/source parameters and the absence of a fuller account of the response contents.

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?

With 0% schema description coverage the description must carry all parameter meaning, and it does so for emails, enforce_invite_only, dry_run, and confirm_write with real behavioral detail. It leaves app_id, code, and especially source entirely unexplained, so half the surface is still undocumented.

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 — add email addresses to a coupon's invite list — plus the default side effect of switching the coupon to invite-only. This is clearly separable from siblings like revoke_coupon_invite and list_coupon_invites without opening any 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 explicit conditional guidance: set enforce_invite_only:false only to stage a list before gating, and use dry_run:true first to preview. It does not explicitly route the agent to sibling tools (revoke_coupon_invite, list_coupon_invites) for the removal or inspection cases, which keeps it just short of a 5.

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