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

io.github.ryanmat/logicmonitor

by ryanmat

get_alerts

Read-onlyIdempotent

Retrieve open or cleared LogicMonitor alerts filtered by severity, device, group, datasource, or time range to focus incident triage and review.

Instructions

Get open or cleared alerts from LogicMonitor, optionally filtered by severity (critical, error, warning), device, group, datasource or time

For Kubernetes clusters, use group_id (from get_device_groups) instead of device; the device name filter does not work reliably for K8s resources.

Common mistakes: startEpoch/endEpoch use SECONDS not milliseconds. String filter values need double quotes (e.g., monitorObjectName:"hostname").

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

Input Schema

NameRequiredDescriptionDefault
ackedNoFilter by acknowledged status
limitNoMax results (max 1000)
sdtedNoFilter by SDT status
deviceNoFilter by device name (substring match)
filterNoRaw filter expression (overrides other filters). Example: severity:4,cleared:false
offsetNoPagination offset
statusNoFilter by status
clearedNoFilter by cleared status
group_idNoFilter by device group ID (matches all devices)
instanceNoFilter by instance name (substring match)
severityNoFilter by severity
datapointNoFilter by datapoint name (substring match)
device_idNoRead this device's own alert list; every other filter applies there except group_id, which is refused beside it
end_epochNoFilter alerts started before this epoch timestamp
datasourceNoFilter by datasource/template name (substring match)
start_epochNoFilter alerts started after this epoch timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / device_id / description
      Previous value: -"Filter by device/resource ID"New value: +"Read this device's own alert list; every other filter applies there except group_id, which is refused beside it"
  2. First observedv4.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, and the description goes further by disclosing two real failure modes: the K8s device-name filter does not work reliably, and startEpoch/endEpoch are in seconds, not milliseconds. It still says nothing about result volume, pagination behavior, or how far back the time range can reach.

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?

Three short blocks, front-loaded with purpose and followed by the two gotchas an agent would otherwise get wrong. Every sentence carries actionable information with no restatement of the name or title.

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?

For a 16-parameter read tool with full schema coverage and rich annotations, the description supplies the non-obvious operational details that matter for correct invocation. It leaves return shape and pagination expectations unaddressed, though with no output schema that gap is less costly here.

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%, so the baseline is 3, but the description earns extra credit by adding semantics the schema lacks: the valid severity tiers, the required double-quoting for string filter values, the epoch unit, and the group_id substitution rule for K8s. It does not explain how the raw filter parameter interacts with the typed filters beyond the schema's 'overrides other filters' note.

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 (get alerts from LogicMonitor) plus the scope of optional filters (severity, device, group, datasource, time), which separates it from detail-oriented siblings like get_alert_details. It does not explicitly name an alternative tool for a narrower alert query, so it stops 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?

Gives concrete conditional guidance: for Kubernetes clusters use group_id rather than device because the device name filter is unreliable there. It does not say when to prefer a sibling such as analyze_alerts or get_apm_service_alerts, so context is clear but exclusions are absent.

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