Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_instances

List all managed server instances from configured AWS EC2, OVH, Hetzner, and custom accounts, with optional filters for region, state, or account.

Instructions

List all managed server instances (AWS EC2, OVH, Hetzner, custom servers) of every configured account. Optionally filter by region, state or account. With several accounts of a provider its servers are named '/'; use that form to target one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoInstance state filter (running, stopped, ...).
regionNoFilter by region or provider (e.g. 'us-east-1', 'custom', 'OVH').
accountNoOnly this account's servers: an account label, or 'custom' for the custom servers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.28.0
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Only this account's servers: an account label, or 'custom' for the custom servers.",
+  "type": "string"
+}
  2. Addedv2.24.0
  3. Removedv2.23.8
  4. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results span every configured account and multiple providers and explains the '<account>/<name>' naming convention, but says nothing about return format, pagination, or volume for accounts with many servers.

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?

Three tight sentences with the core scope front-loaded and no filler. The final sentence on the '<account>/<name>' form is dense but earns its place by enabling precise targeting.

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 read-only, no-argument list tool with 100% schema coverage and no output schema, the description covers scope, providers, optional filters and the multi-account addressing scheme. Only return format/pagination is unaddressed, which is minor here.

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%, so the schema already documents the three filter parameters; the description mostly restates them ('filter by region, state or account'). It does add the meaningful naming-convention hint for targeting a single server, but the parameters themselves gain little beyond the schema.

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?

The description states a specific verb (List) and resource (managed server instances) and clarifies scope: every configured account across AWS EC2, OVH, Hetzner and custom servers. It implicitly distinguishes itself from the provider-specific aws_* siblings by being the cross-provider fleet lister, but it never names a competing tool to make that routing explicit.

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?

It says results can be filtered by region, state or account, which implies when the filters are useful, but gives no when-to-use/when-not guidance and does not point to alternatives (e.g. get_server_info for a single host). Usage is left to inference.

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

Deploy Server

Other Tools