Skip to main content
Glama
Sign In
Windows Developer MCP Server

Windows Developer MCP Server

by peeyushcodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

docker_list_containers

List Docker containers, with an option to include stopped ones for a complete view of running and stopped instances.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
all_containersNoIf True, include stopped containers.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It merely says 'List Docker containers' and does not state that it is a read-only operation, that it lists running containers by default, or that it requires Docker daemon access. This is minimal and lacks transparency.

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, concise sentence with no redundant words. It is appropriately sized for such a simple tool and is front-loaded with the core purpose.

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?

Given the tool's simplicity and the presence of an output schema, the description plus parameter schema provide a basic understanding. However, it omits the default behavior (only running containers) and any usage context, leaving gaps that must be inferred from the parameter description and tool name.

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?

The input schema fully documents the single parameter 'all_containers' with description 'If True, include stopped containers.' Since schema coverage is 100%, the description need not add extra parameter meaning. The baseline of 3 is appropriate as the schema does the heavy lifting.

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 'List Docker containers' uses a specific verb and resource, clearly stating what it does. It distinguishes from sibling tools like docker_list_images (images) and other docker commands, though it doesn't elaborate on scope or variations.

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?

No guidance is provided on when to use this tool vs alternatives like docker_logs or docker_run. There is no mention of preferred contexts, exclusions, or when to avoid using it, leaving the agent to infer usage solely from the 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