Skip to main content
Glama

Redeem a coupon

redeem_coupon

Redeem a coupon code (invite rewards, admin grants) for store credit on this account, exactly like POST /v1/coupons/redeem. Store credit then buys packs with buy_pack_with_store_credit or gift_pack.

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": {
      "code": "<code>"
    },
    "name": "redeem_coupon"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesthe coupon code, e.g. from an invite reward
tokenNothe token your login returned; pass it when a call answered not_logged_in after you logged in

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "the token your login returned; pass it when a call answered not_logged_in after you logged in",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world call, so the safety profile is covered. The description adds that credit lands "on this account" and anchors behavior to POST /v1/coupons/redeem, but says nothing about what happens on an invalid, expired, or already-redeemed code, which matters most given idempotentHint=false.

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 dense sentences with no filler: the action and its effect come first, then the follow-on tools that consume the resulting credit. Nothing is buried or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the token parameter's failure-recovery path is documented in the schema. For a one-shot, non-idempotent mutation the remaining gap is failure semantics and sibling disambiguation, which the description leaves open.

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?

Schema description coverage is 100% and the schema itself explains both code and the conditional token usage thoroughly, so this dimension is already carried by structured data. The description only contributes the examples of code provenance (invite rewards, admin grants) without adding format or validation details 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?

"Redeem a coupon code ... for store credit on this account" gives a specific verb, resource, and effect, and the parenthetical (invite rewards, admin grants) narrows which codes qualify. It stops short of naming redeem_gift_code or gift_code_pack as the contrasting siblings, so an agent must still infer which redeem tool applies to which code type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description routes the agent forward, telling it store credit is then spent via buy_pack_with_store_credit or gift_pack, which is genuine contextual guidance. It gives no explicit when-not guidance and no differentiation from redeem_gift_code or gift_code_pack, which are the most likely mis-selections among the siblings.

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