Skip to main content
Glama

create_containers

Creates multiple Docker containers from a specified image, using a count and base port to expose each instance. Use it to provision repeated container instances for testing or scaling.

Instructions

Crea múltiples contenedores Docker a partir de una imagen

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image": "<image>",
      "count": "<count>",
      "port": "<port>"
    },
    "name": "create_containers"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYesPuerto base a exponer
countYesNúmero de contenedores a crear
imageYesNombre de la imagen Docker (ej: nginx, redis:7, postgres:15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It says containers are created in bulk but not whether they are started, how they are named, what a partially failed batch leaves behind, or what the call returns — all critical for a mutating, fan-out operation.

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 front-loaded sentence with no filler. It is efficient, though its brevity is part of what leaves behavior under-specified.

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

Completeness2/5

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

For a mutating bulk-create tool with no annotations and no output schema, the definition omits the essentials an agent needs: the return value (container IDs/names?), port allocation behavior across the batch, and error/partial-failure semantics.

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%, so all three parameters (image, count, port) are already documented with examples. The description adds only the framing 'from an image' and nothing about how the single base port is distributed across count containers, so the baseline 3 applies.

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?

States a specific verb and resource: creating multiple Docker containers from an image. The verb 'create' contrasts naturally with the siblings list_containers and delete_container, though the description never names or explicitly distinguishes them.

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 on when to use this versus listing or deleting containers, no prerequisites (e.g. whether the image must already be pulled locally), and no conditions under which it should not be called.

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