Skip to main content
Glama
Sign In
MCP DevOps Kit

MCP DevOps Kit

by Jmfrodero
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

docker_stats

Monitor container resource usage in real-time or get a snapshot of CPU, memory, and I/O statistics for all or specific Docker containers.

Instructions

Get resource statistics for containers

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
container_idNoContainer ID or name (optional for all)
streamNoStream statistics (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'get resource statistics' without explaining what the statistics include, whether the container must be running, or the effect of the 'stream' parameter. This lack of detail leaves significant gaps for an agent.

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?

The description is a single sentence, front-loaded with the verb 'Get'. It contains no redundant words and is appropriately sized for the stated purpose. Every word earns its place.

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

Completeness2/5

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

Given the tool has two parameters, no output schema, and no annotations, the description is incomplete. It does not explain the return format, the meaning of 'statistics', or how streaming works. The agent would lack essential context for correct invocation.

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 both parameters. The description adds no extra meaning beyond 'statistics', failing to explain how container_id and stream affect the operation. Baseline 3 is appropriate as the description does not degrade but does not enhance.

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 clearly states the tool gets resource statistics for containers, distinguishing it from sibling tools like docker_logs (logs) and docker_ps (listing). However, it does not specify what resource statistics entails (e.g., CPU, memory), which could be more precise.

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?

The description implies when to use this tool—to get resource statistics—but provides no explicit guidance on when not to use it or how it compares to alternatives like docker_ps or docker_stats (itself). There is no mention of prerequisites or context.

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