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

io.github.ryanmat/logicmonitor

by ryanmat

get_alert_rule

Read-onlyIdempotent

Retrieves details for a specific LogicMonitor alert rule by rule ID, with an option to return the full raw REST object instead of a summary.

Instructions

Get details about a specific alert rule

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": {
      "rule_id": "<rule_id>"
    },
    "name": "get_alert_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full REST object (every field the API returns) instead of the summary
rule_idYesAlert rule 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 and idempotency profile is fully covered structurally. The description adds nothing beyond that: no note on error behavior for unknown IDs, no auth/scoping caveats, and no mention of what the summary versus full object contains.

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 zero padding, appropriate format for a simple getter. It is efficient but borderline under-specified rather than wasteful.

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 two-parameter read-only getter with full schema coverage and rich annotations and no output schema, the definition is minimally sufficient. It still leaves open the distinction between a summary and full REST object at the description level and gives no routing guidance within a large family of similarly named get_* 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 description coverage is 100%, with both rule_id ('Alert rule ID') and raw ('Return the full REST object... instead of the summary') documented inline. The description contributes no additional parameter meaning, 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 ('Get details') and a singular resource ('a specific alert rule'), which lets an agent tell it apart from the plural sibling get_alert_rules without opening the schema. It does not, however, name any sibling explicitly or explain how it differs from near-neighbors like get_alert_details or get_alert_settings.

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 phrase 'a specific alert rule' implies single-record retrieval by ID, but there is no explicit when-to-use statement, no mention of alternatives such as get_alert_rules for listing, and no prerequisites. An agent must infer the use case entirely from the name and required rule_id.

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