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

io.github.ryanmat/logicmonitor

by ryanmat

get_collector_health

Read-onlyIdempotent

Check collector health to investigate outages: see whether collectors are down, downstream device counts, uptime, optional alert history, and recent status checks/events as evidence.

Instructions

Enriched collector status: whether each collector is down, downstream device count, uptime, and optional alert history. Leading indicator for site-level events. Prefer this over get_collectors when investigating potential outages. The collector asked for by collector_id, and each collector not known to be up, carries evidence: its latest status check and its five latest events.

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

Input Schema

NameRequiredDescriptionDefault
collector_idNoSingle collector ID. Other scope args are ignored if set.
history_daysNoHistory lookback in days
include_historyNoInclude recent alerts on a device named for the collector's hostname. A collector with no such device returns an empty list, which does not show it stayed up. The API cannot narrow rows to CollectorDown; each row's alert_type names what it is. A failed read is null with history_warning, not an empty list.
collector_group_idNoRestrict to collectors in this group

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / include_history / description
      Previous value: -"Include recent alerts on a device named for the collector's hostname. A collector with no such device returns an empty list, which does not show it stayed up. The API cannot narrow rows to CollectorDown; each row's alert_type names what it is."New value: +"Include recent alerts on a device named for the collector's hostname. A collector with no such device returns an empty list, which does not show it stayed up. The API cannot narrow rows to CollectorDown; each row's alert_type names what it is. A failed read is null with history_warning, not an empty list."
  2. Changed2 schema fields changedv4.3.0
    • changedInput schema / properties / history_days / description
      Previous value: -"CollectorDown history lookback in days"New value: +"History lookback in days"
    • changedInput schema / properties / include_history / description
      Previous value: -"Include CollectorDown alert history"New value: +"Include recent alerts on a device named for the collector's hostname. A collector with no such device returns an empty list, which does not show it stayed up. The API cannot narrow rows to CollectorDown; each row's alert_type names what it is."
  3. First observedv4.2.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description does not contradict them. It adds behavior beyond the annotations: the default scope returns every collector not known to be up with their latest status check and five latest events, and it flags that this is an outage-indicator view rather than a full inventory.

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 content is front-loaded with the resource and payload, followed by the sibling preference, then the scoping detail; no sentence is pure filler. The final sentence ("The collector asked for by collector_id, and each collector not known to be up, carries evidence...") is grammatically tangled and could be tightened.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so reasonably (down state, device count, uptime, alert history, latest status check, five latest events). Missing pieces are minor — no note on pagination or result-size limits for the unscoped case.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: when collector_id is supplied it scopes to that collector, and otherwise the result set is implicitly the collectors not known to be up. It does not elaborate on history_days or include_history beyond the already-detailed schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Enriched collector status" names a specific resource plus the enrichment (down state, downstream device count, uptime, optional alert history), and the description explicitly distinguishes itself from get_collectors. An agent can tell what this returns without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Prefer this over `get_collectors` when investigating potential outages" gives an explicit alternative and the condition that selects it, plus a framing as a "leading indicator for site-level events." It stops short of stating when not to use this tool (e.g., for plain inventory listing), so it is strong but not complete routing guidance.

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