Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

list_devices

Lists all monitored Observium devices with hostname, IP, OS, hardware, uptime, and status, filtered by OS or state. Use it to discover device IDs before querying ports, sensors, or trends.

Instructions

List all devices monitored by Observium with their current status.

Returns hostname, IP, OS, hardware model, uptime, and polling status for each device. Use this to discover what devices exist before drilling down with other tools.

RETURNS: Array of devices with:

  • device_id: Unique identifier (use with other tools)

  • hostname: Device hostname or IP

  • os: Operating system (linux, ios, junos, etc.)

  • hardware: Hardware model

  • uptime: How long since last reboot

  • status: Current state (up, down, disabled)

  • last_polled: When Observium last collected data

EXAMPLE QUESTIONS:

  • "What devices are monitored?"

  • "Show me all Linux servers"

  • "What devices are currently down?"

  • "List all network switches"

NEXT STEPS: Use device_id or hostname with get_device, list_ports, list_sensors, get_trends

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

Input Schema

NameRequiredDescriptionDefault
os_filterNoFilter by OS type (examples: 'linux', 'ios', 'junos', 'dlink', 'unifi')
status_filterNoFilter by device status

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?

With no annotations supplied, the description carries the full burden, and it does substantial work: it enumerates every returned field, explains their meaning (device_id as the reusable key, last_polled as collection recency, status values up/down/disabled), and thereby establishes the read-only nature implicitly. It does not address result-set size, pagination, or permission requirements for large Observium instances, which is the remaining gap.

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 purpose statement and return-field list are front-loaded and well structured with labeled RETURNS, EXAMPLE QUESTIONS, and NEXT STEPS sections. The example questions section is somewhat padded for a straightforward list tool, and 'What devices are monitored?' largely restates the opening sentence.

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 must explain the return shape, and it does so field by field with types and semantics. Combined with fully documented filter parameters, an agent has what it needs to call this correctly; only edge cases like large result sets and pagination behavior remain unaddressed.

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%, so both os_filter and status_filter are already documented in the schema, making 3 the baseline. The description never references the filters directly; the example questions ('Show me all Linux servers', 'What devices are currently down?') only hint that such filtering is possible, adding no syntax or format detail beyond the schema.

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 ('List all devices monitored by Observium with their current status') and immediately frames the tool's role as the discovery entry point before drilling down with other tools. That framing cleanly separates it from siblings like get_device, list_ports, and get_trends.

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 gives explicit when-to-use guidance ('Use this to discover what devices exist before drilling down with other tools') and a NEXT STEPS section naming concrete follow-up tools (get_device, list_ports, list_sensors, get_trends). It stops short of stating when this tool should NOT be used, but the discovery-then-drill-down sequencing makes the boundary with siblings clear.

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