Reads a one-time, read-only snapshot of Docker container CPU and memory usage on a local or remote homelab host, so you can check resource use without streaming.
One-shot Docker container CPU/memory usage (read-only, like 'docker stats --no-stream')
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | Server name from HOMELAB_HOSTS (e.g. 'sil-baru'). Omit to run on the local machine. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does disclose two non-obvious traits: the operation is read-only and it is a terminating one-shot snapshot rather than a streaming tail. It does not mention permissions, host prerequisites, or the shape of the returned metrics, so it is helpful but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single line that front-loads the resource and behaviour with zero filler; the parenthetical is dense but every clause (one-shot, read-only, --no-stream analogy) earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter, read-only stats tool with full schema coverage and no output schema, the definition supplies enough to call it correctly. A brief note on what metrics or format come back would make it fully self-sufficient, but little is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the single optional 'host' parameter is fully documented in the schema, including the HOMELAB_HOSTS convention and the local-machine default. The description adds nothing about parameters, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: reads one-shot CPU/memory usage for Docker containers, with the analogy 'docker stats --no-stream' pinning the exact semantics. It is clearly separable from siblings like docker_ps and docker_logs by resource, though it does not name an alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
'One-shot' and '--no-stream' imply this is for a single snapshot rather than continuous monitoring, which is useful context. However, no when-to-use guidance, prerequisites, or explicit sibling routing (e.g. use docker_ps to enumerate containers) is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.