Skip to main content
Glama

Axad

Redeem a gift code

redeem_gift
Destructive

Redeem a gift code the learner was given: what it gives is added to their account at once (credit, more cards in the bag, more open practices; any of them may be 0), and the code is used up for good. Returns what the code added and the new credit.

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_gift"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description goes beyond them: it states the grant types applied (credit, cards in the bag, open practices), that any component may be 0, and that the code is permanently consumed. What is not covered is failure behavior — an invalid, expired, or already-redeemed code — which matters for a destructive, non-idempotent action.

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?

One sentence with the purpose front-loaded, an embedded list of possible grant types, and the permanence warning and return value at the end. The parenthetical is informative rather than padding, and nothing repeats the annotations verbatim.

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?

With no output schema, the description correctly explains what comes back (what the code added plus the new credit), and it discloses the side effects of a destructive mutation. It stops short of describing error outcomes for bad codes, which is the one gap for a redeem-token tool.

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?

There is a single parameter with 0% schema description coverage, so the description must carry the meaning. It adds that the value is a gift code issued to the learner (not an internal identifier), but gives no format, length, or case-sensitivity hints, so the compensation is only partial.

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?

The description opens with a specific verb+resource pairing ("Redeem a gift code") and immediately defines the scope as a code the learner was given, so it cannot be confused with any sibling in the list (all of which are browse/show/lesson/card tools). The exact effect is spelled out: grants are applied immediately and the code is consumed.

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?

Usage is only implied by "the learner was given", which suggests the situation (a learner presents a gift code), but there is no explicit when-not, no prerequisites (e.g., must be signed in), and no contrast with any alternative flow. The irreversibility note ("used up for good") functions more as a warning than as usage guidance.

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.