Skip to main content
Glama

delete_container

Deletes a Docker container by name, helping remove unwanted containers to free resources and keep environments organized.

Instructions

Elimina un contenedor Docker por nombre

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": {
      "name": "<name>"
    },
    "name": "delete_container"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre del contenedor a eliminar

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 provided, so the description carries the full behavioral burden, yet it only states that the container is deleted. It does not disclose whether the deletion is forced, whether running containers are rejected, whether the operation is irreversible, or what the tool returns on success or failure — all critical for a destructive 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?

One short, front-loaded sentence with no wasted words or filler. It is arguably too terse for a destructive operation, but from a pure structure standpoint it is efficient and immediately readable.

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 single-parameter tool with full schema coverage, the definition is minimally adequate to invoke it. However, given the destructive nature and the absence of annotations or an output schema, the missing information about irreversibility and running-state handling leaves the definition short of what an agent needs to act safely.

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 "name" parameter already documented in the schema as the container name to delete. The description's phrase "por nombre" reinforces that the target is a name rather than an ID, but adds no format, casing, or ambiguity-resolution detail beyond the schema.

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 ("Elimina") and resource ("contenedor Docker") plus the identifier mode ("por nombre"), so an agent knows exactly what is removed and how the target is addressed. It does not explicitly differentiate itself from sibling tools like list_containers or create_containers, but the verb makes the distinction obvious enough.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites such as whether the container must be stopped first, and no mention of any confirmation or safe-use pattern. The agent must infer everything about appropriate invocation context.

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