Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

list_alerts

Read-only

Retrieve active alerts from LogicMonitor with simple search or advanced filtering. Filter by severity, acknowledgement status, device, or time to find critical issues requiring attention.

Instructions

List active alerts in LogicMonitor (LM) monitoring.

Returns: Array of alerts with: id (alertId), severity (critical/error/warning), resource name, datasource, datapoint, alert message, start time (startEpoch), acknowledgement status (acked), alert rule.

When to use:

  • Get all critical production alerts

  • Find unacknowledged alerts needing attention

  • Monitor specific service health

  • Check CPU/memory alerts

  • Generate alert reports

Two search modes:

  • Simple search: Use query parameter with free text (e.g., query:"prod-web-01") - searches by resource/device name (monitorObjectName field)

  • Advanced filtering: Use filter parameter with LM filter syntax (e.g., filter:"severity:critical,acked:false") for precise control

Common filter patterns:

  • Critical alerts: filter:"severity:critical"

  • Unacknowledged: filter:"acked:false"

  • Specific device: filter:"monitorObjectName~*prod-web-01*"

  • CPU alerts: filter:"resourceTemplateName~*CPU*"

  • Recent alerts: filter:"startEpoch>1730851200" (epoch seconds)

  • Combined: filter:"severity:critical,acked:false" (AND logic)

Query vs Filter:

  • query: Simple text search by resource/device name only (e.g., query:"production", query:"k8s-cluster")

  • filter: Precise LM filter syntax with any alert field. Use for severity, acked status, etc.

  • If both provided, query is converted to filter and combined with provided filter using AND logic

Important: Alert API does NOT support OR operator (||). Use comma for AND only. For complex queries, make multiple calls.

Important: A negative "total" value in the response indicates incomplete results. Use pagination (size/offset parameters) or set autoPaginate: true to retrieve all items.

Related tools: "get_alert" (full details), "acknowledge_alert" (acknowledge), "add_alert_note" (add notes), "generate_alert_link" (get URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSimple search query. Free text (e.g., "prod-web-01", "k8s-cluster") searches by resource/device name (monitorObjectName). Can also use filter syntax (e.g., "severity:critical") which gets formatted automatically.
sizeNoNumber of results per page (default: 50, max: 1000).
offsetNoStarting offset for pagination (default: 0). Use this to skip a specific number of results.
autoPaginateNoAutomatically fetch all pages (default: false). When true, fetches all results across multiple pages. When false, returns only the requested page. Use false for large result sets to avoid long response times.
filterNoFilter expression using LogicMonitor query syntax. Examples: name:*prod*, displayName~*server*, id>100, hostStatus:normal. Available operators: : (equals), ~ (includes), !: (not equals), !~ (not includes), >: (greater than or equals), <: (less than or equals), > (greater than), < (less than). Multiple conditions: Use comma (,) for AND, use || for OR. Do NOT use &&.
fieldsNoComma-separated list of fields to include in response. Examples: "id,displayName,hostStatus" or use "*" for all fields. Omit this parameter to receive a curated set of commonly used fields.
needMessageNoWhether to include alert message details
Behavior5/5

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

Annotations indicate readOnlyHint=true, and the description adds behavioral details such as autoPaginate behavior, negative total meaning, and the conversion of query to filter. No contradiction with annotations.

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?

The description is well-structured with sections (Returns, When to use, Two search modes, Important notes) and front-loaded with purpose. While slightly verbose, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description provides a comprehensive overview of return fields, pagination, modes, and limitations. It fully equips the agent to use the tool correctly.

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?

All 7 parameters have schema descriptions (100% coverage), and the description adds extra context: distinction between query and filter, conversion rules, and common filter patterns. This goes beyond the schema.

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 description clearly states the tool lists active alerts in LogicMonitor and specifies the return structure. It distinguishes from sibling tools like get_alert, acknowledge_alert, etc., by providing context on related functionalities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The 'When to use' section lists concrete scenarios (critical alerts, unacknowledged, etc.) and explains two search modes with guidance on when to use each. It includes important notes about OR operator limitations and negative total handling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/monitoringartist/logicmonitor-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server