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

io.github.ryanmat/logicmonitor

by ryanmat

get_alert_rules

Read-onlyIdempotent

List alert rules with their priority and escalation chain, so you can see which rules route matching alerts where. Supports pagination and filters by rule name or priority.

Instructions

List alert rules: each rule's priority and the escalation chain it routes matching alerts to

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoPagination offset
name_filterNoFilter by rule name (substring match)
priority_filterNoOnly rules of this priority

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv5.0.1
    • addedInput schema / properties / name_filter
      Added value: +{
      +  "description": "Filter by rule name (substring match)",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Pagination offset",
      +  "type": "integer"
      +}
    • addedInput schema / properties / priority_filter
      Added value: +{
      +  "description": "Only rules of this priority",
      +  "type": "integer"
      +}
  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, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds useful context about what the response contains (priority, escalation chain), but says nothing about ordering, pagination behavior, or how the list relates to get_alert_rule. With annotations carrying the behavioral burden, this is adequate but thin.

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?

A single front-loaded sentence with no filler, and the core action comes first. The trailing clause is slightly awkwardly phrased ("it routes matching alerts to") but still compact and informative.

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 read-only list tool with a fully documented schema and rich annotations, the essentials are present, but the description does not distinguish this from the singular get_alert_rule sibling, which is the main ambiguity an agent would face. No output schema exists, yet only one partial sentence is spent describing the return shape.

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% — limit, offset, name_filter and priority_filter are all documented in the schema itself, including the substring matching semantics for name_filter. The description adds no parameter-level meaning beyond that, so the baseline of 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?

"List alert rules" is a specific verb plus resource, and the clause about priority and escalation chain tells the agent what each item carries. It stops short of differentiating itself from the singular sibling get_alert_rule or from get_action_rules, so an agent must infer which one to pick.

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 contains no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_alert_rule for a single rule or get_action_rules for a different rule family. The agent is left to infer selection from the name alone.

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