Skip to main content
Glama

docker_inspect_network

Retrieve detailed Docker network information including connected containers to analyze network configuration and container connectivity.

Instructions

Get detailed info about a Docker network including connected containers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNetwork ID or name

Implementation Reference

  • The inspectNetwork function executes the 'docker network inspect' command using the Docker client.
    export async function inspectNetwork(args: Record<string, unknown>): Promise<string> {
      const docker = getDockerClient();
      const id = args.id as string || args.name as string;
      if (!id) throw new Error("Network ID or name is required");
    
      const network = docker.getNetwork(id);
      const info = await network.inspect();
    
      const lines = [
        `Name:     ${info.Name}`,
        `ID:       ${info.Id.substring(0, 12)}`,
        `Driver:   ${info.Driver}`,
        `Scope:    ${info.Scope}`,
        `Internal: ${info.Internal || false}`,
        `IPAM:     ${info.IPAM?.Driver || "default"}`,
  • Tool definition for docker_inspect_network in the Docker tools suite.
      name: "docker_inspect_network",
      description: "Get detailed info about a Docker network including connected containers",
      inputSchema: {
        type: "object" as const,
        properties: {
          id: { type: "string", description: "Network ID or name" },
        },
        required: ["id"],
      },
    },
  • Dispatch logic for docker_inspect_network inside handleDockerTool.
    case "docker_inspect_network": return inspectNetwork(a);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a read operation ('Get'), it doesn't mention permission requirements, rate limits, error conditions, or what format the detailed info will be returned in. The description provides basic intent but lacks important operational context.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a single-parameter tool and front-loads the essential information.

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 read-only tool with 100% schema coverage but no annotations and no output schema, the description provides adequate basic context about what information will be returned (network details and connected containers). However, it doesn't address important operational aspects like error handling or response format that would be helpful for an AI agent.

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?

Schema description coverage is 100% with the single parameter 'id' well-documented as 'Network ID or name'. The description doesn't add any additional parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 the verb 'Get' and the resource 'detailed info about a Docker network including connected containers'. It specifically distinguishes itself from sibling tools like docker_inspect_container and docker_inspect_image by focusing on networks rather than containers or images.

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?

The description implies usage when detailed network information is needed, but doesn't explicitly state when to use this tool versus alternatives like docker_list_networks (for listing) or docker_inspect_container (for container details). No explicit exclusions or prerequisites are mentioned.

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/batu-sonmez/infraclaude'

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