Skip to main content
Glama

AceRound AI Interview Copilot

redeem_gift_code

Redeem a gift code; its contents are added to this account immediately. Each code can be redeemed once per account. Use get_gift_code_info to preview it. (Requires the user's sign-in with scope account:write.)

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

Input Schema

NameRequiredDescriptionDefault
codeYesGift code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations mark this as non-read-only, non-destructive and closed-world, but the description adds the critical traits the annotations cannot express: the redemption is immediate and one-shot per account, and it requires an account:write sign-in scope. That one-per-account limit is the key irreversibility fact an agent must know before invoking.

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?

Three compact sentences plus an auth note: action and effect first, then the one-per-account constraint, then the alternative tool and the credential requirement. Nothing is redundant and the most decision-relevant facts are front-loaded.

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 one-parameter mutation tool with no output schema, the definition covers effect, rate/eligibility limit, prerequisite auth scope, and a routing alternative. An agent has everything needed to decide and to call it correctly.

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 coverage is 100% with a single required string parameter bounded to 1–64 characters, so the schema already carries the parameter semantics. The description only says "gift code" and adds no format, source, or normalization hints beyond that; baseline 3 applies.

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 ("Redeem a gift code") plus the concrete effect ("its contents are added to this account immediately"), so the agent knows exactly what changes. It also names a distinct preview tool, separating it from get_gift_code_info rather than leaving the agent to guess.

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?

It explicitly routes the agent to get_gift_code_info for previewing before redeeming, which is real when-to-use guidance. What it doesn't state is any exclusion, e.g. what to do with an already-redeemed or invalid code, or whether redemption should always be preceded by a preview.

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