Skip to main content
Glama
Sign In
opsgate

opsgate

by polymatx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go

docker_stats

Fetch a one-shot snapshot of container CPU and memory usage. Specify a host or use the default to monitor resource consumption.

Instructions

Show a one-shot snapshot of container CPU and memory usage.

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": "docker_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNotarget host name from the opsgate config; omit for the default host

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/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 burden, and it does disclose one real behavioral trait: the call is a one-shot snapshot rather than a stream. It omits other behavior an agent needs, such as whether stats cover every container on the host, whether any filtering is possible, and whether the daemon/host must be reachable.

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 front-loaded sentence with no filler; the key qualifier ('one-shot snapshot') is placed immediately after the verb, so the reader gets scope and behavior in one pass.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema, the description is minimally adequate but thin: it never indicates the granularity (per-container vs. aggregate), the metrics returned, or how results are scoped to the host. Nothing is wrong, but more could reasonably be said.

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% and the single 'host' parameter is fully documented in the schema (opsgate config host name, optional). The description adds no extra meaning about the parameter, so the baseline 3 applies.

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 (Show) and resource (container CPU and memory usage), and the phrase 'one-shot snapshot' distinguishes it from streaming/log-tailing siblings like docker_logs. It does not explicitly name a sibling, but the snapshot framing makes its role against docker_ps/docker_inspect reasonably clear.

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?

There is no explicit when-to-use guidance: nothing says whether it covers all containers or one, when to prefer it over docker_ps, docker_inspect, or process_top, or what prerequisites exist. The only hint is the implicit contrast of 'one-shot' versus continuous monitoring.

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