Skip to main content
Glama

面灵AI 面试助手

list_pending_subscription_cards

Read-only

列出用户已购买但尚未激活的会员卡(下单时选择「稍后激活」的卡),以及每张卡能否原路退款、可退金额。(需要用户授权,范围 account:read)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_pending_subscription_cards"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered structurally. The description adds genuinely new behavioral context that annotations cannot express: it requires user authorization with the account:read scope, which tells the agent authorization must be in place before calling.

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?

A single front-loaded sentence names the resource, then parenthetically pins down the exact card state, then adds the refund attributes and the auth scope. Every clause carries information and nothing is repeated from the schema or annotations verbatim.

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?

With no parameters and no output schema, the description carries the burden of describing results, and it does so at a useful level: the list contents plus per-card refundability and refundable amount. It stops short of describing item fields or ordering, which is a minor gap for a list tool but not a blocking one.

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 tool takes zero parameters, so there is nothing to disambiguate beyond the scope wording already given. Baseline for a no-parameter tool is 4, and nothing in the description muddies the (empty) schema.

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 states a specific verb plus resource (list purchased-but-not-activated membership cards) and narrows the scope explicitly to cards where 'activate later' was chosen at checkout. It also declares the secondary payload (refund eligibility and refundable amount), which lets an agent distinguish it from activation/refund siblings without opening any 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?

The trigger context is clear: use this when the user has bought cards that are not yet activated. It implies the follow-up actions (activate vs. refund) by exposing refund eligibility, but it never names a specific sibling or states an explicit 'do not use this for X' exclusion.

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