Skip to main content
Glama

Redeem a Quo gift card

redeem_gift

Redeem a Quo gift card code onto the verified phone number as ride credit. Requires session_token from verify_code.

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

Input Schema

NameRequiredDescriptionDefault
codeYesThe gift card's own code, as printed or emailed to the recipient when it was purchased, not a ride booking code
session_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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-idempotent, closed-world write. The description adds real context beyond them: the credit lands on a verified phone number and the session must come from verify_code, which tells the agent the auth path and that no phone parameter is needed. It does not address the non-idempotency risk (whether a retry double-redeems) or what happens on an invalid/already-used code.

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 short sentences, front-loaded with the action and its effect, then the prerequisite. No redundant restatement of the title and no filler.

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?

For a credit-granting mutation with no output schema and no annotations covering outcomes, the description omits what a successful redemption returns (credit amount, new balance) and what failure modes exist (invalid code, already redeemed, expired). The core call semantics are covered, but the agent is left guessing about results and error handling.

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 50%: `code` is well documented in the schema, while `session_token` is bare. The description compensates by stating the session token originates from verify_code, and "onto the verified phone number" makes clear the target account is implied rather than passed as a parameter. That closes the main semantic gap for this two-parameter tool.

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 Quo gift card code onto the verified phone number as ride credit" gives a specific verb (redeem), a specific resource (Quo gift card code), and the effect (ride credit applied to the verified number). It is unambiguous and distinct from siblings like reserve_and_pay or get_quote, though it does not explicitly name a sibling it could be confused with.

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 prerequisite "Requires session_token from verify_code" implies this must be used after verification and is a follow-on step, which is useful sequencing guidance. However, there is no statement of when not to use it, what to do if the code is invalid or already redeemed, or how it relates to payment/booking tools.

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