Skip to main content
Glama

AceRound AI Interview Copilot

list_pending_subscription_cards

Read-only

List the user's purchased passes that have not been activated yet (bought with delayed activation), and whether each can be refunded and for how much. (Requires the user's sign-in with scope 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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, and the description adds genuinely new context: the required sign-in and the account:read scope, plus what each record reports about refundability and amount. It does not cover pagination or ordering, which keeps it short of a 5.

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 sentence, front-loaded with the core action and resource, with the auth requirement relegated to a trailing parenthetical where it belongs. The nested parentheses around the activation mode are slightly clunky but cost little.

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 returns, and it does so adequately by naming refundability and refund amount. Auth scope is included; only ordering/pagination and behavior on an empty result are unaddressed, which is minor for a simple read-only list.

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 for the description to disambiguate; the baseline for a no-param schema applies. Nothing in the text misdescribes or anticipates parameters that don't exist.

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 gives a specific verb and resource: list the user's purchased passes that have not been activated yet, and clarifies the acquisition mode (delayed activation) plus the refund-eligibility/amount payload. That makes the scope distinguishable from mutation siblings like activate_subscription_card and refund_subscription_card, though it never names an alternative tool 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?

The state-based framing ("not been activated yet") implies when this list is relevant, but there is no explicit when-to-use/when-not guidance and no pointer to the activation or refund tools that would be the natural next steps. Usage is inferable rather than stated.

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