Skip to main content
Glama
Observium MCP Server

Observium MCP Server

by kdesch5000

get_device

Retrieve comprehensive details for a specific network device by hostname, IP, or ID, including hardware, software, location, uptime, and port, sensor, and alert counts.

Instructions

Get detailed information about a specific device.

Returns comprehensive device details including hardware specs, software version, location, uptime, and counts of associated ports, sensors, and alerts.

RETURNS:

  • device_id, hostname, sysName, IP address

  • os, os_version, hardware model, serial number

  • uptime (formatted), last_polled, last_rebooted

  • location, contact information

  • port_count: Number of network interfaces

  • sensor_count: Number of sensors (temp, voltage, etc.)

  • active_alert_count: Current alerts on this device

EXAMPLE QUESTIONS:

  • "Tell me about the firewall"

  • "What's the uptime of server1.example.com?"

  • "Show details for device 16"

  • "How many ports does the switch have?"

NEXT STEPS: Use list_ports, list_sensors, or list_alerts with this device

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

Input Schema

NameRequiredDescriptionDefault
hostnameNoThe hostname or IP (e.g., 'firewall.local', '192.168.1.1')
device_idNoThe device ID (get from list_devices)

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 are supplied, so the description carries the full load; it does identify this as a read-only retrieval and itemizes the response payload in detail (uptime formatting, last_polled, active_alert_count). It says nothing about failure behavior when neither hostname nor device_id resolves, or about how ambiguous/overlapping identifiers are handled.

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?

Structure is strong and front-loaded: purpose, then returns, then example questions, then next steps. There is some redundancy between the opening summary of returned fields and the full RETURNS list, but since no output schema exists the enumeration earns 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?

For a two-parameter read tool with no output schema, the description supplies the return shape, usage examples and follow-on tools, which is enough to invoke it correctly. The one unresolved ambiguity is that both parameters are optional, and the description never says what happens if neither or both are given.

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% and both parameters carry their own descriptions, including the 'get from list_devices' provenance note, so the schema already does the semantic work. The description adds only indirect hints through example questions (hostname form, numeric device ID), which is the baseline 3 for high-coverage schemas.

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 detailed information about a specific device') and immediately clarifies this is the single-device detail fetch, separating it from the bulk orientation of list_devices. The enumerated return fields (hardware, software, location, port/sensor/alert counts) further pin down what 'details' means, so an agent knows what it is getting 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?

Example questions ('Tell me about the firewall', 'Show details for device 16') and the NEXT STEPS line routing to list_ports, list_sensors and list_alerts give clear when-to-use and follow-on guidance. What is missing is an explicit exclusion, e.g. 'use list_devices to find a device_id or to browse many devices' — the schema hints at list_devices but the description does not state it.

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