Skip to main content
Glama

docs_lookup

Read-only

Look up Docker SDK, CLI, or registry reference documentation by section. List available sections or fetch raw HTML/Markdown content to support Docker API calls and configuration files.

Instructions

Look up Docker SDK/CLI/registry reference documentation by section.

A tool-callable mirror of the docker-docs:// resources, for clients that can't read MCP resources (e.g. Claude Desktop, Cursor). Always registered regardless of DOCKER_MCP_SERVER_DISABLE — looking something up costs nothing and isn't tied to any single Docker feature area — but an individual section still refuses if the domain it documents is disabled, matching the equivalent docker-docs://{section} resource exactly.

Omit section to list every available section with its source URL (same as docker-docs://contents); pass a section name to fetch that page's content (same as docker-docs://{section}). Most useful before constructing an extra_kwargs-style passthrough dict for a tool like container_run/container_create/service_create (their docstrings only list common keys, not every key docker-py accepts), or before writing Compose/Dockerfile/buildx bake-file syntax, which no tool generates.

args: section - Section name (from a no-argument call's index); omit to list all sections instead returns: str - JSON section index (no section) or that section's raw HTML/Markdown content

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Beyond readOnlyHint and destructiveHint annotations, description adds that it mirrors docker-docs:// resources, registers regardless of DOCKER_MCP_SERVER_DISABLE, refuses if domain is disabled, and returns JSON index or raw HTML/Markdown. Provides useful behavioral context.

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?

Well-structured with clear first sentence defining purpose, followed by context, usage guidance, and parameter explanation. Slightly verbose with some redundancy, but every section adds value. Could be trimmed slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete given output schema exists: explains return format (JSON index or raw content), usage context, and parameter behavior. Addresses all aspects needed for an agent to use correctly.

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

Parameters5/5

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

Adds significant meaning beyond input schema: explains that omitting section lists all available sections, and passing a section name (from index) fetches content. Clarifies default behavior and source of valid section names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it looks up Docker SDK/CLI/registry reference documentation by section. It distinguishes from sibling action tools by being a documentation lookup tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises when to use: before constructing passthrough dicts for container_run/container_create/service_create, or before writing Compose/Dockerfile syntax. Explains omitting section lists all, passing section fetches content. Lacks only explicit 'when not to use' but provides clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GavinLucas/docker-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server