Skip to main content
Glama

AceRound AI Interview Copilot

refund_subscription_card

Destructive

Refund an unactivated pass to the original payment method; the pass is voided. Only passes showing a refundable amount in list_pending_subscription_cards qualify. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (Requires the user's sign-in with scope 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.3/5.0
Behavior5/5

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

Goes well beyond the supplied annotations by disclosing that the pass is voided, that the refund goes back to the original payment method, that the operation consumes minutes/credits or creates a payment, that the user must be told the cost and agree first, and that account:write scope is required. These are exactly the consequences an agent needs before invoking a destructive tool.

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?

Three tight clauses front-load the action, the precondition, and the cost/consent rule, with auth as a trailing parenthetical. No filler, though the cost-and-consent clause is packed into a single sentence and could be signposted more clearly.

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 one-parameter destructive mutation with no output schema, the description covers effect, eligibility, cost, consent, and auth. It leaves open what a partial versus full refund looks like and what is returned on success or failure, which are minor gaps for this complexity.

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% and cardId has no documented format in the schema, so the description carries the burden. It partially compensates by indicating the ID should come from list_pending_subscription_cards, but it never states the identifier's form or what an invalid/unknown ID does.

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?

States a specific verb and resource ('Refund an unactivated pass') plus the side effect ('the pass is voided'), which cleanly separates it from list_pending_subscription_cards and activate_subscription_card. An agent can tell what this does without opening the 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?

Gives a concrete qualification gate: only passes showing a refundable amount in list_pending_subscription_cards qualify, and it names that sibling as the source. It does not explicitly say what to do with an activated or non-refundable pass, but the 'unactivated' + 'refundable amount' conditions cover most routing decisions.

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