Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

docker_ps

Read-only

List Docker containers on a remote Linux server over SSH; set all_containers=True to include stopped containers.

Instructions

List Docker containers. Set all_containers=True to include stopped containers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "docker_ps"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes
all_containersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful detail that all_containers changes the result set to include stopped containers, but says nothing about output shape, ordering, or what the required server argument must reference.

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 short sentences, no waste, and the core action is front-loaded before the flag detail.

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 two-parameter read tool with annotations and no output schema, this is close, but the required server argument's meaning is a real gap an agent must resolve externally (likely via list_servers).

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 0%, so the description carries the burden. It explains all_containers well (its effect of including stopped containers), but the required server parameter is left entirely undefined — neither schema nor description says what a valid server identifier is.

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 and resource: "List Docker containers." That is enough to separate it from docker_images and docker_logs, but the description never explicitly contrasts with those siblings, so it stops short of a 5.

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?

Usage is only implied by the name and the mention of stopped containers; there is no explicit statement of when to choose this over docker_images, docker_logs, or docker_compose. The running-vs-all distinction is the only hint at a selection condition.

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