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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_flows

Read-onlyIdempotent

Retrieves a NetFlow exporter device's recent flow records, including source/destination IP, port, DNS name, ASN, protocol, and bytes, with pagination; reports FEATURE_DISABLED when NetFlow is off.

Instructions

List a NetFlow exporter device's flow records over the last hours_back hours, rows as the API returns them; the API reference gives each flow its source and destination IP, port, DNS name and ASN, its protocol and its bytes. 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_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety bar is low. The description nonetheless adds real behavior: rows are returned verbatim as the API gives them, the per-flow field set is spelled out, and the FEATURE_DISABLED response is disclosed for devices with NetFlow off — meaningful context an agent cannot get from annotations. It stops short of describing pagination behavior or what an empty result looks like.

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?

Two sentences, front-loaded with the verb+resource+time window, then the return shape, then the failure mode. Every clause carries information; the field enumeration is dense but directly useful for deciding whether the result answers the question.

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 four parameters, no output schema, and no nested objects, the description covers the essential contract: what rows represent, what fields they carry, and the one distinctive error condition. Only pagination-over-limit behavior and a note that this is per-device raw data versus any aggregated sibling remain unaddressed.

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%, so all four parameters are already documented including defaults and the 'ending now' anchor for hours_back. The description reinforces the time window but adds no format, bounds, or paging semantics beyond the schema; 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?

Specific verb and resource: "List a NetFlow exporter device's flow records over the last hours_back hours" tells the agent exactly what data comes back and for which entity. It is scoped narrowly enough to be distinguishable from aggregate siblings, but it never names an alternative (e.g., top-talkers style aggregation) to sharpen that boundary.

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?

Usage is implied by the scope rather than stated: an agent can infer this is the tool for raw per-device flow rows. There is no explicit when-to-use/when-not guidance, no mention of what to do with limit/offset, and no direction on alternatives for aggregated or cross-device views.

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