Skip to main content
Glama

docs_lookup

Read-only

Fetch Docker SDK, CLI, and registry reference documentation by section. Use it to discover accepted parameters and syntax before building container configurations or Compose 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
Behavior5/5

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

Annotations already indicate readOnlyHint and destructiveHint, but the description adds substantial behavior: always registered regardless of DOCKER_MCP_SERVER_DISABLE, per-section refusal if the domain is disabled, the listing-vs-fetch behavior, and the return type (JSON index or raw HTML/Markdown). This is rich behavioral context beyond the annotations.

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 somewhat long but each sentence earns its place: purpose, registration behavior, parameter behavior, use cases, and return format. It is front-loaded with the core purpose and structured logically, though it could be slightly tightened without losing value.

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?

For a simple tool with one optional parameter and an output schema, the description is comprehensive. It covers what the tool does, when to use it, edge cases (disabled domains), and return formats, leaving no significant gaps.

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?

The schema only has 'section' with a default null and no description (0% schema coverage), so the description must compensate. It fully explains the parameter: 'section - Section name (from a no-argument call's index); omit to list all sections instead,' and also describes the return values for both cases, making the semantics clear.

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 uses the specific verb 'Look up' with the resource 'Docker SDK/CLI/registry reference documentation by section,' clearly distinguishing it from all sibling tools, which are operational commands. It also explains it's a mirror of docker-docs:// resources, adding specificity.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance: 'Most useful before constructing an extra_kwargs-style passthrough dict... or before writing Compose/Dockerfile/buildx bake-file syntax, which no tool generates.' It also notes that it serves as an alternative for clients that can't read MCP resources, and explains when sections refuse, giving clear exclusions.

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/L337-org/docker-mcp'

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