Skip to main content
Glama

面灵AI 面试助手

activate_subscription_card

Destructive

激活一张未激活的会员卡:从此刻开始计时,已有生效中的会员时接续在其后;激活后不能再退款。卡 ID 取自 list_pending_subscription_cards。会消耗用户的时长、次数或产生付款,执行前向用户说明扣费内容并取得同意。(需要用户授权,范围 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": {
      "cardId": "<cardId>"
    },
    "name": "activate_subscription_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses the exact irreversibility (no refund after activation), the billing start time, stacking behavior relative to an existing active membership, and that the operation may consume quota or create a payment. It also flags the required authorization scope and the consent requirement, which the annotations do not convey.

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?

The description is dense and front-loaded: the action, the timing and stacking rules, and the irreversibility come first, then ID sourcing, then the consent and authorization requirement. Every clause carries operational information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive mutation, the definition covers timing semantics, stacking, irreversibility, quota or payment effects, ID sourcing, consent, and authorization scope. There is no output schema, and none is needed for the agent to call this correctly.

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?

The single parameter has 0% schema description coverage, so the description must supply its meaning; it does by stating that cardId is taken from list_pending_subscription_cards, which tells the agent how to obtain a valid value. It still omits format or validity details, but the essential semantics are covered.

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?

The description pairs a precise verb with a precise resource ("激活一张未激活的会员卡") and immediately states the key consequences: timing starts from now, the card stacks after any active membership, and it cannot be refunded. This distinguishes it clearly from refund_subscription_card and from read-only listing siblings.

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?

The definition gives a concrete precondition (only unactivated cards), a concrete source for the required ID (list_pending_subscription_cards), and a mandatory consent step before execution, plus the account:write authorization scope. It stops short of stating explicit exclusions or failure cases, so it is not a full when-to-use and when-not-to-use guide.

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