Skip to main content
Glama

面灵AI 面试助手

redeem_gift_code

领取一个礼包码(含代理商兑换卡),权益立即计入当前账号;每个码每个账号只能领一次。可先用 get_gift_code_info 查看内容。(需要用户授权,范围 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
codeYes礼包码或兑换卡密

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 declare it as a non-read-only, non-destructive, closed-world write. The description adds substantive context beyond that: benefits are credited immediately to the current account, redemption is irreversible per account per code, and user authorization with the account:write scope is required. It does not describe the response or what happens if the code was already redeemed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Effect and the once-per-account restriction are front-loaded, with the preview hint and auth scope bracketed afterward. Dense and largely waste-free, though the trailing parenthetical mixes an authorization requirement into what reads as an aside.

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 one-parameter, no-output-schema redemption tool this covers the essentials: what is credited, the idempotency limit, the prerequisite inspection tool, and the required auth scope. Missing only failure behavior such as an already-redeemed or invalid-code result.

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% and the single parameter's description already states it accepts a gift code or redemption card secret. The prose mentions the same two code types, so it adds no format, validation, or sourcing detail beyond the schema; 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?

Names a specific verb (领取/redeem) and resource (礼包码/兑换卡), and explicitly widens scope to cover agent redemption cards. It also points at the sibling get_gift_code_info as the inspection counterpart, so an agent can separate the two without opening either schema.

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?

Gives clear usage context: preview with get_gift_code_info first, and the per-account once-only rule that constrains when this call is valid. It stops short of explicit when-not-to-use or failure handling guidance, which keeps it below 5.

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