Skip to main content
Glama

revoke_coupon_invite

DestructiveIdempotent

Withdraw one address's right to spend a coupon: the targeted block. WRITE, human-gated: a real write requires an elicitation-capable client and the human sees the address and its current status; 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). Works on an address that was never invited too, writing a revoked tombstone, so blocking someone does not depend on whether they were on the list and survives a later bulk re-invite. This only blocks FUTURE redemptions: if the status was already redeemed the discount has been granted, and undoing that means cancelling or refunding the subscription in the dashboard. Prefer this over delete_coupon when one recipient misbehaves -- deleting the code punishes every other invitee. Use list_coupon_invites first to see the current status.

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

Input Schema

NameRequiredDescriptionDefault
codeYes
emailYes
app_idYes
reasonNo
dry_runNo
confirm_writeNo

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

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

Goes well beyond the annotations: discloses the elicitation/human-gate requirement, the SPARK_PAY_MCP_ALLOW_UNELICITED_WRITES escape hatch, confirm_write and dry_run behavior, and the tombstone-write semantics that survive later bulk re-invites. It also scopes the effect to FUTURE redemptions only, which is critical behavior the annotations cannot express.

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?

Dense but front-loaded: the action and write-gating come first, then edge cases, then sibling routing. Every sentence carries operational information with no restatement of the name or title.

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?

For a destructive, open-world write with no output schema, the description covers safety gating, idempotency implications, and failure/skip conditions thoroughly. The only gap is the undocumented `reason` and `app_id` parameters, which slightly under-serve the call site.

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 0%, so the description must compensate: it explains confirm_write, dry_run (works anywhere), and frames email as the targeted address. However, the `reason` and `app_id` parameters are never mentioned, leaving two of six parameters without any semantic guidance.

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: 'Withdraw one address's right to spend a coupon: the targeted block.' It also explicitly distinguishes itself from delete_coupon, so an agent can tell it apart from sibling mutation tools without opening a schema.

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?

Explicit routing: 'Prefer this over delete_coupon when one recipient misbehaves -- deleting the code punishes every other invitee' and 'Use list_coupon_invites first to see the current status.' It also defines when the tool is not sufficient (already `redeemed` requires dashboard cancellation/refund).

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