Skip to main content
Glama

EQVPS — VPS and code sandboxes for AI agents

Top up balance

topup_balance

Create a top-up invoice and return a checkout_url (crypto checkout page on eqvps.com: USDT/USDC on Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Avalanche and Solana, USDC on Base, USDT on TON and Tron; PYUSD, cbBTC, BTC, ETH, BNB, POL, SOL, GRAM, TRX, LTC, DOGE, DASH, BCH, XRP, XLM; Monero (XMR)). The balance is credited automatically once the on-chain payment confirms. amount is in account currency (USD); minimum and maximum are enforced server-side. Only one unpaid top-up may exist at a time. Requires: token. A HUMAN must pay checkout_url in crypto; the balance is credited automatically after confirmation.

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": {
      "amount": "<amount>"
    },
    "name": "topup_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesRequired. Top-up amount in USD (account currency), number 3–10000, e.g. 25. The checkout shows the crypto amount.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / amount / description
      Added value: +"Required. Top-up amount in USD (account currency), number 3–10000, e.g. 25. The checkout shows the crypto amount."
  2. First observed

TDQS

A4.2/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=false, destructiveHint=false) by explaining that the balance is credited automatically once the on-chain payment confirms, that a human must pay the checkout URL, that only one unpaid top-up may exist at a time, and that min/max are enforced server-side. These are exactly the operational constraints an agent needs, since a failed call leaves an open invoice.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The critical facts (purpose, automatic crediting, one-unpaid-invoice limit, human payment) are front-loaded and clear. However, the long parenthetical enumerating dozens of chains and tokens (USDT/USDC, PYUSD, cbBTC, GRAM, etc.) is marketing detail that does not help an agent decide to call the tool and bloats the definition.

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?

No output schema exists, but the description names the key return value (`checkout_url`) and the credit timing, and it covers prerequisites and constraints. It could be clearer about what other invoice identifiers are returned, but it is sufficient for a one-parameter tool.

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 100% and the single `amount` parameter is already documented with a 3–10000 range and examples. The description restates that amount is in USD and that limits are server-side, adding only marginal meaning beyond the schema, so the baseline of 3 applies.

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 concrete verb and resource: 'Create a top-up invoice and return a `checkout_url`'. It is clearly distinguishable from siblings such as `get_balance` (read balance) and `pay_invoice` (pay an existing invoice).

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 strong context: requires token, only one unpaid top-up may exist at a time, and a human must complete the crypto payment, which implies this is the starting point of a two-step flow. However, it never explicitly names alternatives such as `get_balance` or `pay_invoice`, so the agent must infer that this tool creates the invoice rather than paying it.

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.