Skip to main content
Glama

Airsockfly

Redeem reward

redeem_reward
DestructiveIdempotent

Exchange loyalty points for a reward. This spends points: confirm the reward and its cost with the user and set confirm to true only after explicit agreement. Physical rewards need a shipping address.

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": {
      "slug": "<slug>",
      "idempotencyKey": "<idempotencyKey>",
      "confirm": "<confirm>"
    },
    "name": "redeem_reward"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity for shipping a physical reward.
slugYesReward identifier (slug) from list_rewards.
phoneNoPhone number without the country prefix.
streetNoStreet and number for shipping a physical reward.
confirmYesMust be true. Set it only after the user explicitly confirmed this action.
fullNameNoRecipient name for shipping a physical reward.
postalCodeNoPostal code for shipping a physical reward.
countryCodeNoShipping country as a two-letter ISO code.
idempotencyKeyYesUnique key of 8 to 100 characters that you generate once per attempt. Repeating it never creates a duplicate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial 'why': this spends points, and the confirm flag is a consent gate that must not be set unilaterally. That is real value beyond the structured fields, though it says nothing about failure modes (insufficient balance, out-of-stock) or what the tool returns on success.

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 what the tool does, then the irreversible cost, then the conditional requirement. No filler or restatement of the 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 9-parameter mutation with no output schema, the description covers the safety-critical parts: what is consumed, the confirmation gate, and the conditional address requirement. It is slightly thin on outcome expectations (what the caller receives after redemption) given there is no output schema to fall back on.

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 100%, so the baseline is 3, but the description earns an extra point by explaining the conditional requirement that the shipping fields are only needed for physical rewards and by framing confirm as an explicit-consent switch rather than a plain boolean. The remaining address fields' individual meanings are left entirely to 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?

"Exchange loyalty points for a reward" gives a specific verb (exchange) and resource (reward), and the follow-on sentence makes the cost model explicit. It does not name a sibling such as list_rewards for browsing, so an agent must infer the browse-vs-redeem split from the slug parameter's schema text.

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 states a clear precondition workflow: confirm the reward and its cost with the user, and set confirm to true only after explicit agreement, plus the shipping-address requirement for physical rewards. It stops short of exclusions, e.g. what to do when the user has insufficient points or wants to compare rewards first.

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