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

io.github.ryanmat/logicmonitor

by ryanmat

get_action_chains

Read-onlyIdempotent

Lists action chains: ordered DiagnosticSource and RemediationSource stages that action rules trigger on alerts, with pagination for inspecting automated diagnostics and remediation workflows.

Instructions

List action chains: ordered DiagnosticSource/RemediationSource stages that action rules trigger on alerts (Automated Diagnostics & Remediation)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_action_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoResults to skip for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • removedInput schema / properties / name_filter
      Removed value: -{
      -  "description": "Filter by chain name (substring, client-side)",
      -  "type": "string"
      -}
  2. First observedv4.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds domain context about ordered stages and alert-triggering rules, but does not add operational behavior such as pagination or return format. With annotations carrying the main behavioral signals, a 3 is appropriate.

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 a single front-loaded sentence with no wasted wording. The parenthetical domain label is useful but slightly less essential than the main definition.

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?

This is a simple list tool with only two optional pagination parameters, rich annotations, and no output schema. The description sufficiently explains the resource and domain meaning, though it could say more about when to use this listing tool versus the singular get_action_chain.

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 both parameters (limit and offset) already have clear descriptions. The tool description adds no parameter-specific meaning beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description uses a clear verb and resource: 'List action chains,' then explains what an action chain is with ordered DiagnosticSource/RemediationSource stages triggered by action rules. It implicitly differs from the singular sibling get_action_chain by saying 'List,' but does not explicitly name or contrast with it.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives. It only implies that this is the listing form of action chains, without saying when to choose it over get_action_chain or related tools such as get_escalation_chains or get_action_rules.

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