Skip to main content
Glama

Get a per-GB connection line

get_traffic_connection
Read-onlyIdempotent

Read-only, free. Get one ready connection line for the account's per-GB traffic: host, port, username and the traffic key as password, for the residential or the shared mobile network in one country. The line is a secret: keep it in the user's own configuration. Using it spends the account's GB. Needs an API key or an agent token of an ipvolt account.

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": {
      "network": "<network>",
      "country": "<country>"
    },
    "name": "get_traffic_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesTwo-letter country code, for example US.
networkYesresidential, or mobile for the shared mobile pool.
protocolNohttp (default) or socks5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive) it discloses a real cost model (fetch is free, actual use burns GB), the auth requirement (API key or agent token) and a handling constraint (the line is a secret to keep in user config). That is substantial context the annotations cannot express. It stops short of rate limits or line-stability/reuse behavior.

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 two facts an agent needs first ('Read-only, free'), then scope, return payload, and constraints. Sentences are short and earn their place, with only mild repetition between the free-fetch and GB-spend statements.

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?

There is no output schema, so the description must carry the return contract, and it does: host, port, username, and password-as-traffic-key. It also covers the credential-handling obligation, the spend implication, and the auth prerequisite, which is everything needed to call this correctly and treat the result safely.

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 schema already documents country format, the residential/mobile enum, and the http/socks5 protocol. The description only reinforces that the network choice is residential versus shared mobile pool in a single country; the protocol parameter is never mentioned, so it adds little beyond the schema.

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?

States a specific verb and resource: 'Get one ready connection line for the account's per-GB traffic', and lists exactly what is returned (host, port, username, traffic key as password). It scopes the resource to per-GB traffic in one country, which implicitly separates it from rental/purchase siblings, but never names an alternative tool explicitly.

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?

Usage context is implied by 'Using it spends the account's GB' and the auth requirement, so an agent knows the cost gate and prerequisite. There is no explicit when-to-use/when-not statement, and no routing to siblings such as get_rental or list_traffic for non-per-GB cases.

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