Skip to main content
Glama
zb-ss

Servonaut

by zb-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

docker_stats

Collect read-only CPU, memory, and PID metrics for all running containers on a specified instance, returning JSON to monitor resource usage.

Instructions

Single-sample resource usage for every running container on one instance: CPU %, memory used/limit (bytes), memory %, and PID count. Read-only. Returns JSON: {containers: [{name, cpu_percent, mem_used_bytes, mem_limit_bytes, mem_percent, pids}]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instance_idYesInstance ID or name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.23.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, but description declares read-only, single-sample nature, and return format. Adequately discloses behavior without omission.

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, no redundancy. Front-loaded with metrics and return type. Every word serves a purpose.

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?

Given single parameter and no output schema, description covers purpose, metrics, return format, and read-only constraint. No gaps.

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 already describes instance_id as 'Instance ID or name.' Description adds little beyond schema (coverage 100%), so baseline of 3 is appropriate.

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?

Clearly states the tool retrieves single-sample resource usage (CPU, memory, PIDs) for all running containers on one instance. Distinguishes from siblings like docker_ps and docker_logs.

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?

Explicitly mentions it works on one instance and is read-only. While it doesn't contrast with alternatives, the context is clear enough for correct tool selection.

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