Skip to main content
Glama

redeem_gift_card

DestructiveIdempotent

Apply a gift card to an in-person purchase. Use the card ID and an amount in its currency's minor units. Reuse the same idempotency key on retry.

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": {
      "id": "<id>",
      "amount": "<amount>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "redeem_gift_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNo
amountYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds the minor-units currency convention and the idempotency-key retry behavior, which is useful operational context. It does not explain what gets destroyed (e.g., card balance drained, partial redemption allowed) or failure modes, leaving some behavioral gaps.

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 short sentences, front-loaded with the core action and followed by key parameter and retry details. Every sentence earns its place with no wasted wording.

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?

Given the mutation nature and the annotations covering safety hints, the description adequately explains the core mechanics and idempotency. However, with no output schema and 0% schema coverage, it leaves important details unexplained: currency handling, partial redemption behavior, note usage, and error responses. It is minimally sufficient but not complete.

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 0%, so the description must compensate. It explains 'id' as the card ID, 'amount' in minor units, and 'idempotencyKey' reuse on retry, covering three of four parameters. The optional 'note' parameter is not mentioned at all, leaving a gap.

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?

States a specific verb and resource: 'Apply a gift card to an in-person purchase.' This clearly distinguishes it from issue_gift_card or void_gift_card, though it doesn't name siblings explicitly. The scope 'in-person purchase' further narrows it.

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?

Implies usage context ('in-person purchase') and gives retry guidance with the idempotency key. However, it doesn't state when not to use this tool or mention alternatives like redeem_loyalty_reward. Guidance is present but incomplete.

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