Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

list_sensors

Retrieve current sensor readings—temperature, voltage, fan speed, power—across monitored devices, with status against configured thresholds and optional filters by device or sensor type.

Instructions

List sensors (temperature, voltage, frequency, etc.) across devices.

Returns current sensor readings with status relative to configured thresholds. Sensors are auto-discovered via SNMP from devices that support environmental monitoring.

RETURNS: Array of sensors with:

  • sensor_id: Unique identifier

  • hostname: Device the sensor belongs to

  • sensor_class: Type (temperature, voltage, frequency, fanspeed, power, humidity)

  • sensor_descr: Sensor name/description

  • value: Current reading with unit

  • status: normal, warning, or critical (based on thresholds)

  • limits: Configured thresholds (critical_high, warning_high, warning_low, critical_low)

SENSOR CLASSES:

  • temperature: CPU, chassis, ambient temps (°C)

  • voltage: Power supply, rail voltages (V)

  • frequency: CPU, clock frequencies (Hz/MHz)

  • fanspeed: Cooling fan RPM

  • power: Power consumption (W)

  • humidity: Environmental humidity (%)

EXAMPLE QUESTIONS:

  • "What's the hottest sensor?"

  • "Show all temperature readings"

  • "Are any sensors in warning or critical state?"

  • "What's the CPU temperature on the server?"

TIP: Filter by sensor_class to focus on specific sensor types

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

Input Schema

NameRequiredDescriptionDefault
hostnameNoFilter by device hostname
device_idNoFilter by device ID
sensor_classNoFilter by sensor type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the data source (SNMP auto-discovery from environmental-monitoring devices) and the meaning of status relative to configured thresholds, but says nothing about pagination, result limits, data freshness, or required permissions for a potentially large cross-device listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well structured and front-loaded with the purpose, but long for a simple list tool. The sensor class list is effectively stated twice (in RETURNS and again in SENSOR CLASSES), and the EXAMPLE QUESTIONS block is largely filler for an agent that already has the purpose sentence.

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?

There is no output schema, so the description must explain return values, and it does so field by field (sensor_id, hostname, sensor_class, value, status, limits) including the threshold semantics behind status. Nothing an agent needs to interpret the response is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: the SENSOR CLASSES section explains what each enum value represents and its unit (°C, V, Hz/MHz, RPM, W, %), which the schema does not. hostname and device_id are left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ("List sensors") plus the scope ("across devices") and enumerates the sensor types covered. An agent can distinguish this from list_devices, list_ports, and list_alerts without opening any 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?

The EXAMPLE QUESTIONS section gives concrete situations that select this tool (hottest sensor, warning/critical states, CPU temperature), and the TIP directs filtering by sensor_class. It stops short of naming an alternative tool or stating when not to use it, so it is clear context rather than full routing guidance.

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