Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

list_available_metrics

Lists available metrics and RRD files for a device, showing what historical trend data can be queried by category such as system, network, sensors, and performance.

Instructions

List available metrics (RRD files) for a device.

Shows what historical trend data can be queried for a specific device. RRD files are created automatically based on what Observium discovers via SNMP.

RETURNS:

  • hostname: Device queried

  • total_rrd_files: Count of available metrics

  • categories: Metrics grouped by type

    • system: la.rrd (load), processor (cpu), mempool (memory), uptime

    • network: port-*.rrd (interface traffic)

    • sensors: sensor-*.rrd (environmental data)

    • performance: poller stats

EXAMPLE QUESTIONS:

  • "What metrics are available for the server?"

  • "Can I get CPU data for this device?"

  • "What historical data exists for the switch?"

NEXT STEPS: Use get_trends with discovered metrics, or get_port_traffic for network data

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

Input Schema

NameRequiredDescriptionDefault
hostnameNoThe device hostname
device_idNoThe 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?

With no annotations, the description carries the full burden and does reasonably well: it discloses that RRD files are created automatically by Observium's SNMP discovery (so the agent knows the list is discovery-driven, not user-defined) and enumerates the return structure by category. It does not state permission requirements or whether the call is strictly read-only, which is a minor gap for a listing tool.

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 is front-loaded in the first sentence, and the RETURNS / EXAMPLE QUESTIONS / NEXT STEPS blocks are scannable and each serve a function. The category breakdown is somewhat verbose for a listing tool, but no sentence is pure filler.

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, and the description compensates well by enumerating the return fields and metric categories. The remaining gap is the unresolved hostname-vs-device_id question, which matters because both parameters are optional and the agent needs to know how to address a device.

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 hostname and device_id are already documented in the schema, and the baseline is 3. The description adds no guidance on the relationship between the two optional parameters — notably it never says whether one is required in practice or which takes precedence — so it does not improve on 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 opening line gives a specific verb and resource ('List available metrics (RRD files) for a device') and immediately clarifies the scope as historical trend data for one device. The parenthetical RRD explanation and the note that files are auto-created via SNMP discovery make it distinguishable from siblings like get_trends and get_port_traffic.

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?

The EXAMPLE QUESTIONS section makes the intended use case concrete ('What metrics are available for the server?'), and NEXT STEPS explicitly routes the agent to get_trends for discovered metrics and get_port_traffic for network data. It stops short of stating when NOT to use this tool, but the alternative routing is clear.

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