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

io.github.ryanmat/logicmonitor

by ryanmat

get_action_rules

Read-onlyIdempotent

List action rules to identify alert conditions—severity, device groups, and datasource matchers—that trigger action chains, with name filtering and pagination.

Instructions

List action rules: alert conditions (severity, device groups, datasource matchers) that trigger action chains

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_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoResults to skip for pagination
name_filterNoFilter by rule name (case-insensitive substring)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / name_filter / description
      Previous value: -"Filter by rule name (substring, client-side)"New value: +"Filter by rule name (case-insensitive substring)"
  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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds useful domain context about what an action rule contains and what it triggers, but says nothing about result volume, default page size behavior, or whether the list is bounded.

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?

One front-loaded sentence with a clear verb and an informative appositive; nothing is redundant. It could be marginally stronger with a routing clause toward the singular sibling, but no wording is wasted.

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?

For a simple read-only list tool with four annotations, a fully described three-parameter schema and no output schema, the description covers what the tool returns conceptually. The main omission is guidance on when to use this versus the singular or related action-chain tools.

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%, so limit, offset and name_filter are already fully documented in the schema. The description adds no parameter-level meaning (e.g., matching semantics or how filtering interacts with pagination) beyond what the schema states, making the baseline 3 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 gives a specific verb+resource ('List action rules') and defines the domain object as alert conditions (severity, device groups, datasource matchers) that trigger action chains, which helps distinguish it from get_alert_rules. It does not, however, explicitly point to the singular get_action_rule sibling for single-record retrieval.

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?

There is no when-to-use guidance, no mention of alternatives such as get_action_rule or get_action_chains, and no indication of when filtering with name_filter is preferable to listing everything. The intended usage is only implied by the verb 'List'.

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