Skip to main content
Glama
io.github.ryanmat/logicmonitor

io.github.ryanmat/logicmonitor

by ryanmat

get_device_top_talkers

Read-onlyIdempotent

Retrieve a NetFlow exporter device's top talkers for the last N hours to show what is consuming WAN bandwidth, by endpoint, port, or graph.

Instructions

A NetFlow exporter device's top talkers over the last hours_back hours, for 'what is consuming my WAN?': by=endpoint pages the endpoints it saw and by=port the ports, rows as the API returns them (the API reference gives each a usage and a share); by=graph returns its top talkers graph whole. Answers FEATURE_DISABLED when the portal has NetFlow off for the device.

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": {
      "device_id": "<device_id>"
    },
    "name": "get_device_top_talkers"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoEndpoints, ports, or the top talkers graphendpoint
limitNoMax rows (endpoint and port)
offsetNoPagination offset (endpoint and port)
device_idYesNetFlow exporter device ID
hours_backNoHours of flows to read, ending now

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive but open-world call, so the safety profile is covered. The description adds value beyond that by disclosing the FEATURE_DISABLED error when NetFlow is off for the device and by explaining that graph mode ignores paging — both are things an agent would otherwise have to discover at runtime.

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

Conciseness3/5

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

It is front-loaded with the resource and use case, which is good, but the single dense sentence is heavily parenthetical and packs mode semantics, return-shape caveats, and an error code into one breath, making it harder to scan than it needs to be.

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 does the work of sketching the return value (usage and share per row, whole graph for by=graph) and names the main failure mode, FEATURE_DISABLED. It could say more about pagination totals or what an empty result means, but an agent has enough to call it correctly.

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?

Schema coverage is 100% and already defines every parameter, but the description adds real meaning on top: it clarifies that limit/offset apply only to the endpoint and port modes while by=graph returns the graph whole, which is a behavioural constraint the schema only hints at. The note that rows come back 'as the API returns them' with usage and share is helpful but defers detail to an external reference.

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 states a specific verb and resource ('top talkers over the last hours_back hours' for a NetFlow exporter device) and frames the intent with 'what is consuming my WAN?'. It never names the neighbouring get_device_flows tool, so an agent must still infer whether top-talkers aggregation or raw flows is the right choice, which keeps it 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 Guidelines4/5

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

It supplies a clear use case ('what is consuming my WAN?') and mode-selection guidance: by=endpoint pages endpoints, by=port pages ports, by=graph returns the whole graph. It stops short of stating when not to use the tool or naming an alternative for raw flow inspection.

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