Skip to main content
Glama

compose_kill

Destructive

Terminate containers in a Docker Compose project immediately by sending SIGKILL (or a custom signal). Use it when you need an abrupt stop; choose compose_stop for a graceful shutdown.

Instructions

Send a signal to a compose project's containers (default SIGKILL).

Immediate, with no grace period — prefer compose_stop for a clean shutdown (stop signal, then kill after a timeout). Does not raise on a non-zero CLI exit — inspect returncode/stderr in the result.

args: services - Restrict to these services (default: all) signal - Signal to send (default "SIGKILL"; e.g. "SIGTERM", "SIGHUP") remove_orphans - Also remove containers for services not in the compose file project_dir - Dir with the compose file (default: server cwd; copied to the target host if no local plugin) files - Explicit compose file paths (repeatable, -f) project_name - Compose project name override returns: dict - {"returncode": int, "stdout": str, "stderr": str, "truncated": bool}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNo
signalNoSIGKILL
servicesNo
project_dirNo
project_nameNo
remove_orphansNo
Behavior5/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds critical behavioral details: immediate execution with no grace period, non-raising behavior on CLI errors, and the exact return shape (returncode/stdout/stderr/truncated). This significantly enriches the agent's understanding beyond what annotations provide.

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 well-structured: a one-line summary, a usage alternative note, a failure-handling note, a compact args list, and a returns line. Every sentence carries necessary information, and the most critical usage guidance is front-loaded. No waste or redundancy.

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?

With 6 optional parameters and no output schema, the description covers all bases: parameter meanings and defaults, return format, error behavior, and when to prefer an alternative. It provides a self-contained guide for invoking this tool correctly, making it fully contextually complete.

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 input schema has zero descriptions (schema_description_coverage=0%), but the description's 'args' section thoroughly explains all six parameters, including defaults (e.g., services default all, signal default SIGKILL) and examples (SIGTERM, SIGHUP). It even notes the behavior of project_dir when no local plugin is present. This fully compensates for the missing schema descriptions.

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 a specific verb ('Send a signal') and resource ('compose project's containers'), clarifies the default signal (SIGKILL), and distinguishes itself from compose_stop by explicitly recommending the latter for clean shutdown. This makes the purpose unambiguous and distinct from siblings.

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 gives explicit guidance on when to use this tool versus compose_stop ('prefer compose_stop for a clean shutdown'), and provides handling instructions for non-zero CLI exits (inspect returncode/stderr). This is strong, actionable usage guidance that covers both selection and error handling.

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