Skip to main content
Glama

Buy the approved credit pack

autoshort_buy_credits
Idempotent

Buy an owner-approved credit pack with the saved card off-session only when auto-recharge is active and within its monthly cap. Reuse an idempotency key to prevent duplicate charges.

Instructions

Buy the owner-approved credit pack on their saved card, off-session — only when auto-recharge is ACTIVE and only within its monthly cap. Idempotent: the same idempotencyKey never charges twice. Returns 202 while Whop processes it; poll autoshort_get_credit_balance. Without auto-recharge use autoshort_get_buy_credits_url.

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": {
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "autoshort_buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotencyKeyYesA new unique key per purchase; reuse it only to retry the same purchase.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true, destructiveHint=false): it discloses that a saved card is charged off-session, that the charge is capped by the monthly auto-recharge limit, and that the call is idempotent per key. It also explains the async contract — a 202 while Whop processes, with balance polling as the follow-up — which no structured field conveys.

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?

Terse and front-loaded — the action and payment mechanism lead, followed by preconditions, idempotency contract, async result, and the fallback route. Every sentence carries distinct operational information; no 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 money-moving mutation with no output schema, it supplies the missing pieces: eligibility gate, idempotency guarantee, success semantics (202 accepted, not completed), and how to observe the outcome. Nothing material is left for the agent to guess.

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?

Schema coverage is 100% and already documents idempotencyKey's uniqueness and retry rule, so baseline would be 3. The description adds meaning the schema does not: that reusing the key never double-charges, and that the key governs retry of a purchase whose result arrives asynchronously via 202.

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 ('Buy the owner-approved credit pack on their saved card, off-session') and immediately scopes it. It is unmistakably distinct from autoshort_get_buy_credits_url (which it names as the non-auto-recharge path) and from autoshort_get_credit_balance (named as the polling target).

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?

Gives explicit preconditions — only when auto-recharge is ACTIVE and only within its monthly cap — plus a named alternative ('Without auto-recharge use autoshort_get_buy_credits_url'). Both the when and the when-not are stated, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.