Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

by monitoringartist
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

get_alert_rule

Read-only

Retrieve complete details of a LogicMonitor alert rule by ID to review matching conditions, escalation chain, suppression settings, and troubleshoot alert routing.

Instructions

Get detailed information about a specific alert rule by ID in LogicMonitor (LM) monitoring.

Returns: Complete alert rule details: name, priority, enabled status, detailed matching conditions (device groups, datasources, datapoints, instance filters, severity levels), escalation chain assignment, suppression windows, notification settings.

When to use:

  • Review exact matching logic before modifying rule

  • Troubleshoot why alert matched (or didn't match) this rule

  • Document alert routing policies

  • Verify suppression settings

  • Check which escalation chain receives matching alerts

Matching conditions explained:

  • deviceGroups: Which resource/device folders this rule applies to (e.g., /Production/, /Database Servers/)

  • datasources: Which datasources trigger this rule (e.g., CPU, Memory, AWS_EC2)

  • datapoints: Specific metrics (e.g., CPUBusyPercent, MemoryUsedPercent)

  • instances: Filter by instance name (e.g., C: drive only, eth0 interface only)

  • severity: Alert levels (critical, error, warn)

  • escalatingChainId: Where matching alerts are routed

Troubleshooting use cases:

  • "Why did this CPU alert go to wrong team?" → Check resource/device group + datasource filters

  • "Why didn't I get paged?" → Verify alert matches conditions AND check escalation chain

  • "Too many alerts" → Review if conditions too broad, add instance filters

Workflow: Use "list_alert_rules" to find ruleId, then use this tool to review complete matching logic and routing.

Related tools: "list_alert_rules" (find rules), "update_alert_rule" (modify), "get_escalation_chain" (check notification chain).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleIdYesThe ID of the alert rule to retrieve
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.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by explaining what details are returned (matching conditions, escalation chain, etc.) and providing context for troubleshooting. No contradictions, but could mention permission needs.

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?

Well-structured with headings and bullet points. The purpose is stated upfront. It is slightly longer but each section earns its place. Could be tightened, but effective for an AI agent.

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 thoroughly explains what the tool returns and provides rich context about matching conditions and troubleshooting. This fully compensates for the missing output schema and 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear parameter descriptions. The description does not add significant new information about the parameters themselves; it focuses on returned fields. Baseline 3 is appropriate.

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 tool clearly states it retrieves detailed information about a specific alert rule by ID, distinguishing itself from sibling tools like list_alert_rules (find rules) and update_alert_rule (modify). The verb 'get' and specific resource 'alert_rule' are precise.

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?

Provides explicit 'When to use' bullet points, troubleshooting use cases, and workflow. It directs users to use list_alert_rules to find the ruleId, and mentions related tools for modification and escalation chain. This fully addresses when to use and alternatives.

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