Skip to main content
Glama

List mobile proxy stock and prices

list_stock
Read-onlyIdempotent

Read-only, free, no credential needed. List the dedicated mobile proxy rentals ipvolt sells now: country, carrier, length (1 or 30 days), price in US cents and whether each is in stock. It never shows stock counts. While per-GB traffic is on sale it also lists the prepaid GB packs with their prices and the countries each shared pool has now. Filter by country, carrier or length. Use it before rent_proxy.

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

Input Schema

NameRequiredDescriptionDefault
daysNoRental length: 1 or 30 days.
carrierNoCarrier name as list_stock shows it, for example Verizon.
countryNoTwo-letter country code, for example US.
includeSoldOutNoAlso list rentals that are sold out now. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive, so the description earns credit for adding facts annotations cannot express: no credentials or cost, prices denominated in US cents, and the explicit limit 'It never shows stock counts.' It also discloses that GB packs appear only conditionally ('While per-GB traffic is on sale'), which prevents an agent from treating their absence as an error. Return format detail beyond field names is absent, keeping it at a 4.

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 access profile and the core listing, then fields, then caveats, then filtering, then the sibling pointer. Nearly every clause carries information, though the parenthetical '(1 or 30 days)' duplicates the enum already defined in the schema.

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?

With four optional parameters, no required arguments and no output schema, the description does the necessary work by enumerating the returned fields and their units. It is missing only edge-case behavior an agent might want, such as whether an empty catalog versus a filtered-out result looks different.

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%, so every parameter already carries its own description, enum and pattern. The description only restates the filterable axes ('Filter by country, carrier or length') and adds no semantics the schema lacks, such as whether filters are AND-combined or how includeSoldOut interacts with pack results. Baseline 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 specific verb and resource plus exactly what is returned: 'List the dedicated mobile proxy rentals ipvolt sells now: country, carrier, length (1 or 30 days), price in US cents and whether each is in stock.' It also carves out a second result set (prepaid GB packs) and implicitly separates the sellable catalog from an agent's own rentals.

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?

'Use it before rent_proxy' gives explicit sequencing guidance against a named sibling, and 'Read-only, free, no credential needed' tells the agent this is a cheap discovery call it can make freely. It stops short of stating when *not* to use it (e.g. to inspect already-owned rentals via list_rentals), so the alternative coverage is partial.

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