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

io.github.ryanmat/logicmonitor

by ryanmat

get_device_delta

Read-onlyIdempotent

Track which LogicMonitor devices changed and how by listing devices to get a delta ID, then querying that ID for changes since it began.

Instructions

List devices/resources through the device delta, to follow what changed. Without delta_id it lists the devices whose display name contains name_filter, or every device, and returns a delta_id; each such read starts a new delta, so keep the first page's. With delta_id it lists the devices changed since that delta started (change says how), every change since then on each read. name_filter is refused there, since the portal answered a filtered read with an empty page that left out a changed device.

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_device_delta"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
delta_idNoThe delta_id an earlier read returned
name_filterNoFilter by display name (substring), without delta_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing delta lifecycle behavior (each unfiltered read starts a new delta, so keep the first page's delta_id), the semantics of subsequent reads ('every change since then on each read'), and a concrete portal limitation that makes name_filter fail with delta_id. This is exactly the kind of operational caveat annotations cannot express, though 'each such read starts a new delta' sits slightly in tension with idempotentHint=true.

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?

Front-loads the purpose, then splits behavior by the delta_id present/absent cases in a logical order. Some sentences are long and the trailing justification about the empty filtered page is wordy, but it explains a real trap rather than padding.

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 necessary work by stating that a delta_id is returned and hinting at a 'change' field on subsequent reads. The return shape is only gestured at, but for a paginated delta lister an agent has enough to call it correctly and interpret the key output.

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, and the description largely restates them. It does add real meaning for one case: name_filter is refused when delta_id is present, and why. That is a genuine increment, but the baseline of 3 fits since the schema carries most of the load.

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?

States a specific verb and resource ('List devices/resources through the device delta') plus the delta-following intent, which clearly separates it from a plain device listing. It does not name any sibling such as get_device, so an agent must infer that get_device is the snapshot alternative.

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?

Gives explicit mode selection: omit delta_id to enumerate/filter devices and obtain a delta, supply delta_id to get only changed devices. It does not state when to prefer a non-delta listing over this tool, leaving the comparison to siblings implicit.

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