Skip to main content
Glama
Sign In

Opservo

by com.getopservo
OverviewDiscussionsAdmin

List servers

list_agents
Read-onlyIdempotent

Lists the servers and Kubernetes clusters in the signed-in Opservo workspace, with each one's agent_id, kind (linux server or kubernetes cluster), hostname, display name and whether it is online. Archived servers are left out.

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed: why, in plain English (unknown server, server from another workspace, not a Kubernetes cluster).
agentsNoServers and clusters in the workspace, most recently seen first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agents": {
+      "description": "Servers and clusters in the workspace, most recently seen first.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "agent_id": {
+            "description": "Server id (UUID) used by every per-server tool.",
+            "type": "string"
+          },
+          "hostname": {
+            "description": "Hostname reported by the agent.",
+            "type": "string"
+          },
+          "kind": {
+            "description": "linux server or kubernetes cluster.",
+            "enum": [
+              "linux",
+              "kubernetes"
+            ],
+            "type": "string"
+          },
+          "log_health": {
+            "description": "Latest log-summary health: healthy, degraded, critical or unknown.",
+            "type": "string"
+          },
+          "name": {
+            "description": "Display name set in Opservo, when it differs from the hostname.",
+            "type": "string"
+          },
+          "online": {
+            "description": "Whether a heartbeat arrived recently.",
+            "type": "boolean"
+          },
+          "tags": {
+            "description": "Tags set in Opservo.",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "agent_id",
+          "hostname",
+          "kind",
+          "online"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "error": {
+      "description": "Present only when the call failed: why, in plain English (unknown server, server from another workspace, not a Kubernetes cluster).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real context beyond that: the exact attributes returned (agent_id, kind, hostname, display name, online status) and the filtering rule that archived servers are excluded. Pagination or result-size behavior is not mentioned.

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

Conciseness5/5

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

Two sentences, zero filler, with the core purpose front-loaded and the archived-server caveat placed last where it belongs. Every clause carries 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?

An output schema exists, so return values need not be explained, yet the prose field list makes the result self-describing anyway. For a zero-parameter, read-only listing tool, nothing an agent needs in order to call it correctly 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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline is 4. The description's field list describes the output shape rather than any input, which is appropriate and adds no confusion.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists the servers and Kubernetes clusters in the signed-in Opservo workspace') and enumerates the fields returned, so the agent knows exactly what the call yields. The plural, whole-workspace scope implicitly separates it from the singular get_* siblings (get_server_overview, get_kubernetes_snapshot), but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the description conveys that this is the enumeration entry point, and the note 'Archived servers are left out' hints at scoping. There is no explicit when-to-use, when-not-to-use, or pointer to get_server_overview for deeper per-server detail.

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

All Opservo toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources