Skip to main content
Glama

Buy credits (returns a payment link or crypto invoice)

buy_credits

Create a credit-package checkout without completing payment. Read get_service_status first. Stripe returns a card checkout link. New crypto checkout is temporarily paused during the Plisio incident. Any actual charge or transfer requires user authorization.

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": {
      "package_id": "<package_id>"
    },
    "name": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoPayment method. 'stripe' = card link (needs a human), 'crypto' = wallet-payable invoice. Default 'stripe'.
currencyNoFor method 'crypto': the coin to pay in; returns a raw wallet address an agent can pay autonomously.
package_idYesThe package id to buy (from get_packages).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses that the call itself is non-charging, that crypto checkout is currently paused due to a named incident, and that funds movement requires user authorization. These are substantive behavioral facts an agent cannot derive from the structured fields. It stops short of describing what the returned object contains or what happens to a stale checkout, but with annotations already covering the safety profile this is strong.

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?

Four short sentences, front-loaded with the purpose and then the prerequisite and caveats, with no filler. Slight redundancy in restating the Stripe-link return value already present in the title, but nothing wasteful.

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 3-parameter checkout-creation tool with no output schema, the description covers the prerequisite, the non-charging nature, the current crypto outage, and the authorization requirement. The main remaining gap is what the agent should do with the returned link/invoice and how long it stays valid, which is a modest omission.

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 description coverage is 100%, and the schema already explains method, currency, and package_id including the human-vs-autonomous distinction. The description adds only the method-level facts about Stripe vs crypto, which largely restate the schema. Baseline 3 applies when the schema carries the parameter burden.

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 first sentence names a specific verb and resource ("Create a credit-package checkout") and immediately scopes it with "without completing payment," which separates it from confirm_credit_bonus and from any tool that reads balances. An agent knows exactly what this tool produces (a payment link or crypto invoice) 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?

It gives an explicit prerequisite ("Read get_service_status first") and an explicit boundary: no charge is made, and real charges need user authorization. It does not state when to use stripe vs crypto beyond the schema enum, or how this relates to confirm_credit_bonus, but the core when-to-use guidance is present and unambiguous.

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.