Skip to main content
Glama

list_containers

Lists all active Docker containers so you can inspect running services and manage container orchestration through natural language commands.

Instructions

Lista todos los contenedores Docker activos

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does contribute one useful behavioral fact — only active/running containers are returned, implying a read-only, non-mutating operation — but says nothing about return shape, ordering, pagination, or failure behavior when Docker is unavailable.

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?

A single short sentence with no wasted words, and the scope constraint ("activos") is front-loaded. It is arguably under-specified rather than over-written, so conciseness itself is not the problem.

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 trivial no-parameter, no-output-schema listing tool, the core intent is covered, and the active-only scoping is the most important behavioral detail. Still missing is anything about the returned collection's format or environment prerequisites, which matters more here because no annotations and no output schema provide that context.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to add; the baseline for this dimension is 4. The description correctly implies the call is unfiltered and complete over the active 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 pairs a specific verb ("Lista") with a specific resource and scope ("contenedores Docker activos"), so an agent can immediately tell this is a read/listing operation. It does not explicitly contrast itself with the create_containers or delete_container siblings, but the listing verb makes the distinction largely self-evident.

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: the "activos" qualifier suggests this is the tool for enumerating running containers, but there is no explicit statement of when to prefer it, whether stopped containers are reachable another way, or any prerequisite such as a reachable Docker daemon. For a zero-parameter listing tool the omission is mild but real.

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