Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

list_proxy_locations

Where a proxy type has IPs online: countries (no country given), or the states and cities of one country. The codes are what a connection takes after the login (cr.us, state.california, city.losangeles).

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": {
      "type": "<type>"
    },
    "name": "list_proxy_locations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe proxy type
stateNoA state code from this tool, to list that state's cities
countryNoTwo-letter country code, e.g. "us", to list its states and cities

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden. It does add useful behavioral detail — the results are locations that currently have IPs online, and the returned codes are exactly what a connection uses post-login — but it says nothing about read-only semantics, permissions, pagination, or what an empty result means.

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?

Two compact sentences with no filler, and the location-hierarchy rule is front-loaded. The phrasing is slightly compressed to the point of being cryptic ("Where a proxy type has IPs online"), but nothing is redundant.

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 three-parameter read-only listing tool with no output schema and no annotations, this covers the essentials: which type is required, how country/state branch the result set, and the shape of returned codes. Only edge cases (invalid country/state, empty availability) are unaddressed.

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 the baseline is 3, but the description genuinely adds meaning beyond the schema: it spells out the interaction between country and state (a state code narrows to that state's cities) and gives concrete code examples that map schema fields to actual returned values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this enumerates the geographies (countries, states, cities) where a given proxy type currently has IPs online, and it names the code format returned (cr.us, state.california, city.losangeles). The verb is implicit ("Where ... has IPs online" rather than "List"), and it never distinguishes itself from the similarly named list_countries sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the call modes well: omit country to get countries, supply a country to get its states and cities, supply a state to get its cities. That is guidance on how to invoke, but not on when to choose this tool over list_countries or other location-listing siblings, and it gives no prerequisites or failure conditions.

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