Skip to main content
Glama

Get guest network counters

proxmox_get_node_netstat
Read-only

Fetches host-side traffic counters for guest tap/veth devices on a Proxmox node, reporting bytes in/out per device and VMID, with optional VMID filtering.

Instructions

Traffic counters of the guests' tap/veth network devices on a node (bytes in/out per device and VMID), as seen from the host.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
vmidNoOnly this guest

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: the counters come from the host's view of tap/veth devices and are broken out by device and VMID, which also compensates for the missing output schema by sketching the return shape.

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?

A single sentence with no filler, front-loading the resource and then the unit and granularity. Every clause (tap/veth, bytes in/out, per device and VMID, host-side view) carries information an agent can use.

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 no output schema present, the description does the required work of describing what is returned: byte counters in and out, keyed by device and VMID. Both optional parameters are documented in the schema, so the remaining need is only minor detail such as whether counters are cumulative or rate-based.

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 both parameters carry descriptions, including the PROXMOX_DEFAULT_NODE fallback and the proxmox_list_nodes pointer. The description adds only that filtering is by node and VMID, which the schema already conveys, so the baseline 3 applies.

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 names a specific resource (traffic counters of guests' tap/veth devices) and scope (per node, per device, per VMID), which clearly separates it from node-level interface or guest-config tools such as proxmox_get_guest_network. It does not explicitly name a sibling it is not, 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. The phrase 'as seen from the host' hints at the vantage point, but nothing tells an agent whether to prefer this over proxmox_get_guest_network or proxmox_get_node_network_interface when traffic data is wanted.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools