Skip to main content
Glama

ipvolt account

Rent a mobile proxy (spends balance)

rent_proxy
DestructiveIdempotent

SPENDS MONEY from the prepaid ipvolt balance of the credential's account. Rent dedicated mobile proxy devices for 1 or 30 days. 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 country, carrier and days (and optional quantity). Needs a read-write API key, an agent token that may buy, or the order's invoice ID.

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": "rent_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoRental length, 1 or 30 days. Required for the preview.
carrierNoCarrier name from list_stock. Required for the preview.
confirmNoLeave out to preview the charge. Set true, with the preview requestId, only after the user approved that charge.
countryNoTwo-letter country code from list_stock. Required for the preview.
quantityNoNumber of devices, 1 to 20. Default 1.
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?

Annotations already flag destructive=true and idempotent=true, but the description adds substantial context beyond them: the actual billing source (prepaid balance), the price-rise refusal behavior, the replay semantics of a confirmed requestId, and the three accepted auth mechanisms. This is exactly the behavioral detail annotations cannot convey.

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-loaded with the money warning, then organized into numbered (1)/(2) steps, so the reader hits the critical constraint first. It is dense and slightly long, but nearly every clause carries operational information; only the final auth sentence feels appended rather than integrated.

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 destructive, no-output-schema mutation tool, the definition covers cost source, workflow, failure mode, idempotency, and authorization. Nothing an agent needs in order to call it safely and correctly is missing.

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%, so baseline is 3, but the description adds genuine meaning: it states that country, carrier and days are needed for the preview step (the schema marks nothing required) and that requestId must be copied exactly from the preview and used only with confirm: true. It does not explain quantity's cap or confirm's default beyond what the schema already says.

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 description opens with a specific verb and resource ('Rent dedicated mobile proxy devices') plus scope ('1 or 30 days') and leads with the highest-stakes fact ('SPENDS MONEY from the prepaid ipvolt balance'). An agent can immediately distinguish this from read-only siblings like get_balance or list_rentals.

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?

It gives an explicit two-step protocol: call without confirm to get a price and requestId, then call again with confirm: true only after user approval. That is a direct when-to-use / when-not-to-use rule with the alternative path (preview) named, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources