Skip to main content
Glama

Get VPS traffic

vps_get_traffic
Read-only

Network traffic of a VPS in the current month: usage (total, in, out), the monthly limit with remaining traffic and vmStatus (normal or throttled once the limit is used up), and a daily log of in and out. For CPU, memory and ping use vps_get_monitoring; for more included traffic, vps_upgrade.

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": {
      "id": "<id>"
    },
    "name": "vps_get_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe VPS ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the current-month scope, the vmStatus semantics (normal vs throttled once the limit is used up), and the presence of a daily log. It stops short of describing response shape detail or units, but that is a minor gap for a read-only getter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence front-loads the resource and its content, the second sentence routes to alternatives. No filler or redundant restatement of the title.

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?

With no output schema, the description takes on the job of explaining the return payload, and it does so thoroughly (usage breakdown, limit/remaining, throttle status, daily log). For a read-only single-parameter getter, nothing an agent needs in order to call it correctly is missing.

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?

Single parameter 'id' with 100% schema description coverage and an explicit pattern, so the schema carries the burden. The description adds nothing about the ID format, but that baseline 3 is appropriate for a one-parameter tool fully documented in the schema.

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?

Specific verb+resource (network traffic of a VPS for the current month) plus an explicit enumeration of returned fields: total/in/out usage, monthly limit, remaining traffic, vmStatus, and a daily log. It is clearly distinct from vps_get_monitoring and vps_upgrade, which are named.

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?

Explicit routing: 'For CPU, memory and ping use vps_get_monitoring' and 'for more included traffic, vps_upgrade' — each alternative is paired with the condition that selects it. An agent can decide between these tools without opening another schema.

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.