Skip to main content
Glama
ryanmat

io.github.ryanmat/logicmonitor

by ryanmat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

create_escalation_chain

Create an escalation chain in LogicMonitor by defining stages, recipient routing, and throttling to control how alert notifications are sent.

Instructions

Create an escalation chain (requires write permission)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the escalation chain
descriptionNoOptional description
destinationsNoList of Chain objects. Each Chain has type ('single' or 'timebased'), optional period object (null for 'single'), and stages (list of stage arrays; each stage is a list of Recipient objects). To route to an LM Integration, use a Recipient with type='admin', addr=<username>, and method=<integration display name>. Lowercase 'admin'. Shorthand {type: 'integration', integration_name: ..., admin: ...} is rewritten to the canonical admin+method form before the request hits the API.
cc_destinationsNoCC Recipient list. Each entry is a Recipient {type, addr, method, contact}. Applied to every stage.
enable_throttlingNoEnable alert throttling
throttling_alertsNoNumber of alerts before throttling
throttling_periodNoThrottling period in minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate this is a write operation (readOnlyHint=false). The description adds a permission requirement, which is mildly useful, but discloses no side effects, failure modes, or open-world implications beyond that.

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?

One short, front-loaded sentence with zero redundancy. Every word is informative and the core purpose is immediately visible.

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

Completeness2/5

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

Despite having 7 parameters, including nested destinations with complex structure啵 the description provides no overall guidance on how to construct a valid chain or when this operation is appropriate. The sparse description defers entirely to the schema, which is insufficient for a tool of this complexity without an output schema.

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 description coverage is 100% and each parameter already has descriptive text. The tool description adds no parameter-level meaning, so the baseline score of 3 applies.

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?

States a specific verb 'create' and resource 'escalation chain', clearly distinguishing it from sibling tools like update_escalation_chain or get_escalation_chains. The action and target are unambiguous.

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

Usage Guidelines2/5

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

Only mentions a prerequisite ('requires write permission') but gives no guidance on when to use this tool vs alternatives such as update_escalation_chain. No contextual cues, exclusions, or conditions are provided.

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