Skip to main content
Glama

Show per-GB traffic: GB left, packs, countries

list_traffic
Read-onlyIdempotent

Read-only, free. Show the account's per-GB traffic: the traffic key's state, GB bought, used and left, the gateway host and ports, the countries the residential and the shared mobile pool have now, and the prepaid packs with their prices. It shows no secret; get_traffic_connection gives a connection line. Needs an API key or an agent token 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": "list_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds real context beyond them: the call is free, it reveals no secret, and it requires an account API key or agent token. The only gap is that it does not disclose rate limits or freshness of the country data.

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 key facts ('Read-only, free') and then a single well-formed enumeration of the returned fields, followed by the disambiguation and auth note. The middle sentence is dense but every clause maps to a distinct piece of information; nothing is filler.

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?

There is no output schema, so the description carries the burden of describing return values, and it does so field by field. Combined with the auth note and sibling disambiguation, an agent has enough to call it correctly; only freshness and error behavior are left implicit.

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?

The tool takes zero parameters, so there is nothing parameter-level to explain; the baseline for a parameterless schema applies. The description instead spends its words on what the output contains, which is the useful substitute here.

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?

Uses a specific verb and resource ('Show the account's per-GB traffic') and then enumerates exactly what is returned: key state, GB bought/used/left, gateway host and ports, countries per pool, and prepaid packs with prices. It also explicitly distinguishes itself from get_traffic_connection, so an agent can separate the two without opening a schema.

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?

The description tells the agent when to prefer the sibling ('get_traffic_connection gives a connection line') and states the credential requirement ('needs an API key or an agent token'). It gives clear context for the read-only reporting role, though it does not explicitly exclude related read tools like get_balance.

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