Opservo

Domains and SSL expiry

get_domains

Read-onlyIdempotent

Returns the domains served by one server's web server configuration and the number of days until each SSL certificate expires.

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The server/agent UUID to query.

Output Schema

Name	Required	Description	Default
`error`	No	Present only when the call failed: why, in plain English (unknown server, server from another workspace, not a Kubernetes cluster).
`domains`	No	Domains from the nginx/Apache configuration.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "domains": {
+      "description": "Domains from the nginx/Apache configuration.",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "days_until_expiry": {
+            "description": "Days until the SSL certificate expires; null when unknown.",
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "domain": {
+            "description": "Domain served by the web server.",
+            "type": "string"
+          },
+          "ssl_error": {
+            "description": "Present when the certificate could not be checked.",
+            "type": "string"
+          }
+        },
+        "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"
+}

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds the scoping constraint that results come only from the web server configuration (so non-web servers may yield nothing), which is modest added value but no detail on permissions, rate limits, or result shape.

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?

A single sentence with zero filler, front-loading both the resource (domains) and the secondary payload (SSL expiry days). Nothing is wasted and nothing important is buried.

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 one-parameter read tool with full annotation coverage and an output schema that already documents the return shape, the description supplies enough to call it correctly. The only shortfall is the absence of any routing guidance among the many sibling read tools.

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% for the single agent_id parameter, so the baseline is 3. The description's 'one server' wording corroborates the schema's 'server/agent UUID' semantics but adds no additional format or constraint detail.

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?

Specific verb ('Returns') plus a precisely bounded resource: the domains in one server's web server configuration and each certificate's days-to-expiry. That resource is inherently distinct from siblings like get_services, get_server_overview, or get_log_summary, so an agent can route 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 Guidelines2/5

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

The phrase 'one server's web server configuration' implies the per-agent query model, but there is no explicit when-to-use, no when-not-to-use, and no mention of any alternative tool despite eight siblings. The agent is left to infer that this is the domain/SSL-specific view.

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

All Opservo tools Inspect

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

Need Help?