Skip to main content
Glama
Sign In
HomeLab MCP

HomeLab MCP

by chip10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

docker_list_containers

List all Docker containers and their current status, enabling quick monitoring and management of containerized services.

Instructions

Lista contenedores Docker y su estado.

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_list_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_containersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It conveys read-only enumeration and promises status information in the output, but it does not clarify whether stopped containers are included by default or describe any further behavioral traits. This is adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler. It is appropriately concise for a one-parameter list tool, though the brevity leaves room for the parameter semantics that would have made it more useful.

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?

An output schema exists, so the return shape is covered elsewhere. However, the description omits parameter semantics and any usage guidance, and with no annotations the overall context is incomplete enough that an agent may not know how to use the all_containers flag effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description does not mention the all_containers parameter. The parameter name and default value of true hint at broad listing, but the agent cannot learn what false means or how it changes the result set.

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, 'Lista contenedores Docker y su estado,' identifies a clear verb and resource: it lists Docker containers and provides their status. It is distinguishable from related Docker sibling tools like docker_container_logs or docker_restart_container by being a listing operation, though it does not explicitly name an alternative.

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 guidance about when to use this tool versus its siblings. The description does not mention that docker_container_logs is for logs or that start/stop/restart operate on the containers listed here, so usage context must be inferred entirely from the tool name.

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