Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

get_alert_summary

Retrieve aggregated alert counts by type, entity, and device to quickly assess current Observium health before drilling into specific alerts.

Instructions

Get a summary of current alert status.

Returns aggregated alert counts by type, entity, and device. Use for quick health overview before drilling into specific alerts.

RETURNS:

  • total_active: Count of currently active alerts

  • total_recovered: Count of recovered alerts (last 7 days)

  • by_entity_type: Breakdown by device/port/sensor

  • by_device: Top devices with most alerts

  • recent_alerts: Last few alerts raised

EXAMPLE QUESTIONS:

  • "How many active alerts are there?"

  • "Which device has the most alerts?"

  • "Give me an alert overview"

  • "What's the current alert situation?"

NEXT STEPS: Use list_alerts for details on specific alerts

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does so well: it enumerates the returned aggregates and even pins down a semantic detail the schema cannot convey ('recovered alerts (last 7 days)') plus ranking behavior for by_device. It stops short of stating read-only semantics, cost/latency, or any limits on how far back 'current' extends, which are the only remaining behavioral gaps.

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?

It is well front-loaded (purpose, then returns, then next steps) and the RETURNS block earns its space because there is no output schema. The four EXAMPLE QUESTIONS are largely interchangeable restatements of the opening sentence and could be cut to one or two without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter aggregate tool with no annotations and no output schema, the description covers everything an agent needs: what it summarizes, what each returned field means, and where to go next. Describing return values is necessary here precisely because no output schema exists, and the definition handles that burden fully.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. Nothing in the text implies hidden or optional inputs that the empty schema omits.

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 description opens with a specific verb and resource ('Get a summary of current alert status') and immediately scopes it as an aggregated overview rather than a detail listing. The 'NEXT STEPS' line explicitly names list_alerts as the detail-oriented sibling, so the boundary between the two is unambiguous 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 Guidelines5/5

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

It states the use case ('quick health overview before drilling into specific alerts') and routes the agent onward to list_alerts for details, which functions as an explicit when-to-use/when-to-switch rule. The example questions reinforce the intended entry-point role for an agent starting an alert investigation.

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