Skip to main content
Glama

面灵AI 面试助手

refund_subscription_card

Destructive

退掉一张未激活的会员卡:款项原路退回付款账户,卡同时作废。只有 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": "refund_subscription_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
cardIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further: it says the refund is returned to the original payment account, the card is invalidated, and the user's quota (time, count) may be consumed or a payment incurred. It also discloses the consent requirement and the account:write scope, which annotations cannot express.

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?

The definition is front-loaded: purpose and effects first, then eligibility, then consent and auth. Every clause carries information, though the final parenthetical auth note and the consent sentence could be tightened slightly.

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 single-parameter destructive mutation with no output schema, the description covers effects, eligibility, side costs, consent, and authorization — everything an agent needs before invoking it. No return-value explanation is required here.

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 0% for the single cardId parameter, so the description must compensate. It does indicate the ID's provenance (cards in list_pending_subscription_cards marked refundable), but it never states the ID format or behavior for invalid/already-refunded IDs, leaving part of the gap.

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 opens with a specific verb and resource ('退掉一张未激活的会员卡') and immediately states the two concrete effects: money returned to the original payment account and the card voided. It also scopes the operation to unactivated cards, which distinguishes it from activate_subscription_card and other card siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the exact precondition for use — the card must appear in list_pending_subscription_cards with a refundable amount — naming the sibling that supplies valid inputs. It adds a mandatory consent step and the required authorization scope (account:write), so when-to-use and prerequisites are both explicit.

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