Skip to main content
Glama
monitoringartist

LogicMonitor MCP Server

get_escalation_chain

Read-only

Retrieve complete escalation chain details including stages, recipients, notification methods, delays, and schedule to review and audit notification workflows.

Instructions

Get detailed information about a specific escalation chain by its ID in LogicMonitor (LM) monitoring.

Returns: Complete escalation chain details: name, description, all stages with: recipients at each stage, notification methods (email/SMS/webhook), time delays between stages, rate limiting, business hours restrictions.

When to use:

  • Review detailed notification workflow

  • Verify who gets notified at each stage

  • Check timing between escalations

  • Audit notification methods

  • Troubleshoot why notifications not received

Stage details returned: For each stage:

  • Stage number (1, 2, 3...)

  • Delay before stage triggers (minutes)

  • Recipients/groups notified

  • Notification methods (email, SMS, integration)

  • Schedule (24/7 vs business hours only)

Example escalation chain details: Stage 1 (0 min): Email "oncall@company.com", SMS "+1-555-1234" Stage 2 (15 min): PagerDuty integration, Email "team-lead@company.com" Stage 3 (30 min): Slack webhook, Email "engineering-manager@company.com"

Workflow: Use "list_escalation_chains" to find chainId, then use this tool to review complete notification workflow.

Related tools: "list_escalation_chains" (find chains), "update_escalation_chain" (modify), "list_recipients" (see recipients).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainIdYesThe ID of the escalation chain 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.
Behavior4/5

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

Description adds context beyond readOnlyHint annotation, detailing return structure and stages. No contradictions. It does not discuss potential limitations like rate limits or auth, but for a read-only lookup, this is acceptable.

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 sections, but slightly verbose with repeated stage details. Front-loaded key info. Still concise enough for utility.

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?

No output schema, but description compensates with detailed return info, example, and workflow. Covers essential requirements for an 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?

Schema coverage is 100%, and description adds meaning: explains fields parameter usage with examples and default behavior. This goes beyond the schema's brief descriptions.

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 it gets detailed information about a specific escalation chain by ID. It distinguishes from sibling tools like list_escalation_chains and update_escalation_chain, making its unique purpose evident.

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?

Explicitly lists when to use: review notification workflow, verify recipients, check timing, audit methods, troubleshoot. Also provides a workflow: use list_escalation_chains first, then this tool. Related tools are named.

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