Skip to main content
Glama

面灵AI 面试助手

get_gift_code_info

Read-only

查询一个礼包码(含代理商兑换卡)包含的权益、是否过期、是否已领完、当前账号能否领取。(需要用户授权,范围 account:read)

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": "get_gift_code_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes礼包码或兑换卡密

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. Beyond that, the description discloses a real operational requirement not in the annotations: user authorization with the account:read scope. It also enumerates the facts returned, which is valuable because no output schema exists.

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?

One parenthetical-free sentence plus an auth note: the core purpose and the enumerated output facts are front-loaded, and the permission requirement is tucked into parentheses where it belongs. There is no wasted wording, though the sentence is dense with comma-separated clauses.

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 single-parameter read-only lookup with no output schema, the description does the necessary work: it lists the four result dimensions an agent will receive and states the authorization prerequisite. Nothing critical is missing, though it does not say what happens when the code is invalid or unknown.

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, and the description earns an extra point by clarifying that the input may be either a gift code or an agent redemption card secret (代理商兑换卡), which widens the expected value beyond the schema's plain '礼包码或兑换卡密' label. No format or length hints are added, but the schema already supplies min/max length.

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?

The description uses a specific verb (查询/query) and resource (礼包码/兑换卡) and enumerates exactly what is reported: contained benefits, expiry, remaining stock, and eligibility for the current account. This is clearly a lookup rather than a redemption, so it is distinguishable from redeem_gift_code, though that sibling is not named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the pre-redemption check step because it reports eligibility and remaining stock. There is no explicit when-not guidance and no named alternative such as redeem_gift_code, so the routing is left to inference.

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