Skip to main content
Glama

Get Bandwidth History

get_bandwidth_history
Read-onlyIdempotent

Retrieves recent WAN throughput samples from a Verizon CR1000A router, helping monitor bandwidth trends over time.

Instructions

Recent WAN throughput samples as a list of integer series.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds that the payload is a list of integer series, but leaves "recent" undefined — no time window, sample interval, or units (bps vs bytes) — which are the details an agent actually needs to interpret the values.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity costs it only where substance was needed, not where words were wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and an output schema present, the description need not explain return values, so the structural burden is small. Still, the undefined "recent" window and unknown units leave an agent unable to say what time span the history covers or how to read the integers.

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 no parameters, so the schema carries no meaning that the description must compensate for; baseline 4 applies. Nothing in the description misrepresents or obscures the parameter situation.

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

Purpose3/5

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

The phrase "Recent WAN throughput samples as a list of integer series" identifies the resource (WAN throughput) and the shape of the result, so an agent can tell it is not the per-host traffic tool. However it is a bare noun phrase with no verb and no explicit statement of what the tool does — retrieve, sample, or stream — and it never names a sibling like get_host_traffic to draw the contrast.

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 guidance at all: nothing says to prefer this over get_host_traffic when the question is about aggregate WAN capacity rather than a single host, and no exclusions or prerequisites are given. The only signal is the word "WAN" in the title, which the agent must interpret unaided.

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