Skip to main content
Glama

Buy a per-GB traffic pack (spends balance)

buy_traffic_pack
DestructiveIdempotent

SPENDS MONEY from the prepaid ipvolt balance of the credential's account. Buy one prepaid pack of GB for residential IPs and for mobile IPs from a shared pool. Two steps: (1) call without confirm: this only looks up the current price and answers the exact charge and a requestId; nothing is charged. (2) Only after the user approved that charge, call again with confirm: true and that requestId. If the price rose meanwhile the API refuses instead of charging more, and repeating a confirmed requestId returns the same order without charging again. The first call needs packId (from list_traffic or list_stock). A pack is bought under the current Terms and Refund Policy, which the dashboard asks the customer to accept at each pack purchase: confirm the pack and its price with the user first. Needs a read-write API key or an agent token that may buy, of an ipvolt account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_traffic_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
packIdNoPack id from list_traffic or list_stock, for example gb:5. Required for the preview.
confirmNoLeave out to preview the charge. Set true, with the preview requestId, only after the user approved that charge.
requestIdNoThe requestId the preview returned, copied exactly. Use it only with confirm: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the destructiveHint/idempotentHint annotations by naming what is actually spent (prepaid balance), explaining the preview-then-confirm handshake, the refusal behavior if the price rose, and the idempotency guarantee that repeating a confirmed requestId returns the same order without a second charge. Auth requirements (read-write key or buying agent token) are also disclosed.

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?

Front-loads the single most consequential fact ('SPENDS MONEY'), then numbers the two steps, then covers edge cases and credentials. Dense but nearly every sentence carries operational weight; the trailing Terms/Refund-Policy sentence is the only one that could be tightened against the user-approval point already made.

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 money-spending mutation with no output schema, the description covers cost implications, the required call sequence, failure behavior on price change, idempotent retry semantics, and authorization — everything an agent needs to avoid an accidental or duplicate charge.

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 the schema already explains packId, confirm and requestId, so the description is not carrying the parameter burden alone. It still adds real value by tying parameters to call order: packId is needed for the preview, and confirm/requestId are only valid together after approval. The pattern examples (gb:5) live in the schema, not the description, so this is not a full 5.

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 one prepaid pack of GB for residential IPs and for mobile IPs') and immediately distinguishes itself from pure lookup siblings by opening with 'SPENDS MONEY from the prepaid ipvolt balance'. An agent can tell this apart from list_traffic, list_stock and get_balance without opening any schema.

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 an explicit two-step procedure, states which call is free, gates the charged call on user approval of the exact price, and names the sibling sources for packId (list_traffic or list_stock). When-to-use and when-not-to-charge are both stated outright.

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