Skip to main content
Glama

AceRound AI Interview Copilot

activate_subscription_card

Destructive

Activate an unactivated pass: it starts now, or right after the current pass if one is active. An activated pass can no longer be refunded. Card ids come from list_pending_subscription_cards. 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": "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?

Annotations already flag destructiveHint=true, but the description adds the concrete consequences: irreversibility of refunds, billing drawn from minutes/credits or a newly created payment, exact activation timing, and the required account:write sign-in scope. This is meaningful behavioral context beyond the structured fields.

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?

Four tight sentences, front-loaded with the core action and its timing rule, followed by the irreversible-cost warning, id provenance, and auth requirement. No sentence is 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 single-parameter, destructive, payment-triggering mutation with no output schema, everything an agent needs is present: sourcing of the id, cost disclosure duty, refund forfeiture, timing, and auth scope.

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?

With 0% schema description coverage on cardId, the description compensates by naming the authoritative source of the id (list_pending_subscription_cards). It adds no format or validation detail, but the maxLength/type constraints are already in the 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?

Specific verb plus resource ('Activate an unactivated pass') with immediate scoping semantics: it starts now or after the current pass. An agent can distinguish this from list_pending_subscription_cards and refund_subscription_card purely from the text.

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?

Explicitly routes the agent to list_pending_subscription_cards for ids and imposes a consent precondition ('tell the user what it costs and get their agreement first'). It stops short of naming when-not-to-use cases such as an already-activated card, though the refund warning implies that boundary.

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