Skip to main content
Glama
AIops-tools

fabric-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

network_traffic

Read-only

Retrieve top applications and protocols by bytes for a Meraki network to analyze traffic mix and identify high-bandwidth usage.

Instructions

[READ] Application/protocol traffic mix for a network, top apps by bytes.

Args:
    network_id: Meraki network id (from network_list).
    timespan: Look-back window in seconds (7200..2592000, default 86400).
    limit: Max rows in the returned list (default 25). The result carries
        'returned'/'limit'/'truncated'; re-run with a higher limit when
        'truncated' is true rather than treating the list as complete.
    target: Target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
limitNo
targetNo
timespanNo
network_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds real behavioral context beyond them: the return payload carries 'returned'/'limit'/'truncated' and truncation must be handled by re-running rather than assuming completeness. It does not cover auth/permission needs, but the truncation contract is the important disclosure for a paginated read.

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?

Purpose is front-loaded in one line, then parameters are laid out in a scannable Args block. Nothing is padded; the note about 'truncated' is the one longer sentence and it directly affects correct usage.

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, the description compensates by naming the returned metadata fields and explaining how to react to truncation. It is nearly complete for a read-only list tool; minor gaps remain around what identifiers the app rows carry, but nothing prevents a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so: network_id provenance, timespan bounds and default (7200..2592000, default 86400), limit default plus truncation semantics, and target's fallback behavior. Each parameter gains meaning absent from the bare schema titles.

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?

The first line states a specific verb and resource: '[READ] Application/protocol traffic mix for a network, top apps by bytes.' It is immediately distinguishable from siblings like client_usage, network_health_score, or device_uplinks, which measure different things.

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?

It gives useful invocation guidance (network_id comes from network_list; re-run with a higher limit when 'truncated' is true; omit target for the default), but never says when to choose this tool over adjacent ones such as client_usage or network_alerts.

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