Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

list_alerts

Retrieve Observium alerts with status and details to troubleshoot device, port, and sensor issues; filter active or recovered alerts for monitoring.

Instructions

List alerts from Observium with status and details.

Returns active or historical alerts including device down, port down, and sensor threshold violations. Use for troubleshooting and monitoring.

RETURNS: Array of alerts with:

  • alert_id: Unique identifier

  • hostname: Affected device

  • alert_name: Type of alert

  • entity_type: What triggered it (device, port, sensor)

  • entity_name: Specific entity affected

  • status: active or recovered

  • timestamp: When alert was raised

  • duration: How long alert has been active

ALERT TYPES:

  • Device alerts: Device down, device rebooted

  • Port alerts: Port down, port errors, port utilization

  • Sensor alerts: Temperature high, voltage out of range

EXAMPLE QUESTIONS:

  • "Are there any active alerts?"

  • "What alerts fired this week?"

  • "Show me all recovered alerts"

  • "What's alerting on the switch?"

NEXT STEPS: Use get_alert_summary for overview, or investigate with get_device/list_sensors

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": "list_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum alerts to return (default: 50, max: 500)
statusNoFilter by alert statusactive
hostnameNoFilter by device hostname
device_idNoFilter by device ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the result shape field-by-field, the alert taxonomy, and the active-vs-recovered distinction. It stops short of stating that this is a non-mutating read, any authentication prerequisites, or result ordering/truncation behavior when the limit is hit.

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?

Strongly front-loaded: purpose first, then returns, then alert types, then alternatives. The RETURNS block is justified because no output schema exists, but the four EXAMPLE QUESTIONS are somewhat padded and one of them is misleading, so the section doesn't fully earn its space.

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?

With no output schema and no annotations, the description compensates well by enumerating return fields and alert categories. The remaining gap is that the unsupported time-based example question creates a false expectation about what can be filtered.

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 the baseline is 3 and the description mostly restates what the schema already documents. Worse, the example question "What alerts fired this week?" implies time-window filtering that no parameter actually supports, which could send an agent looking for a non-existent filter.

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?

The opening line gives a specific verb and resource ("List alerts from Observium") plus the payload ("status and details"), and the NEXT STEPS line distinguishes it from get_alert_summary (overview) and the investigation tools. An agent can tell this apart from its siblings without opening the 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?

It states the general context ("Use for troubleshooting and monitoring") and explicitly routes the agent elsewhere for aggregation (get_alert_summary) and drill-down (get_device/list_sensors). What's missing is a crisp when-not rule tied to the status filter, e.g. when to prefer the summary over the raw list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.