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

io.github.ryanmat/logicmonitor

by ryanmat

get_escalation_chain

Read-onlyIdempotent

Retrieve details for a specific LogicMonitor escalation chain by chain ID, optionally returning the full REST object instead of a summary.

Instructions

Get details about a specific escalation chain

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain_id": "<chain_id>"
    },
    "name": "get_escalation_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object (every field the API returns) instead of the summary
chain_idYesEscalation chain ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / raw
      Added value: +{
      +  "default": false,
      +  "description": "Return the full REST object (every field the API returns) instead of the summary",
      +  "type": "boolean"
      +}
  2. First observedv4.2.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond them: it doesn't say what a null/missing chain yields, what the default summary omits, or that open-world access may be slow or permission-gated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no padding, but it is under-specified rather than economical — the brevity comes at the cost of any routing or behavior detail.

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

Completeness3/5

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

For a simple two-parameter read-only lookup with full schema coverage and annotations, the definition is minimally sufficient. It still omits the relationship to the plural sibling tool and gives no hint about the default summary shape, which matters because there is no 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%, including an explicit description for the raw toggle explaining that it returns the full REST object instead of the summary. The description adds no parameter meaning of its own, so the baseline 3 applies.

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 details about a specific escalation chain') and the word 'specific' implies a single-item lookup by ID. It does not explicitly distinguish itself from the sibling get_escalation_chains (list) or get_action_chain, so differentiation is left to inference.

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?

No when-to-use guidance, no mention of the list counterpart get_escalation_chains, and no prerequisites or exclusions. The agent must infer that this is the single-record fetch versus the collection fetch.

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