Skip to main content
Glama
Sign In
homebutler

homebutler

by Higangssh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

docker_stop

Destructive

Stops a named Docker container to halt a running service; restarting it is manual because no start action is available.

Instructions

Stop a Docker container by name. Nothing here starts it again: there is no start tool, so the operator brings it back themselves

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": "docker_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesContainer name to stop
serverNoRemote server name from config (optional, runs locally if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.2

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds genuinely non-obvious operational context beyond that: there is no start tool, so a stopped container must be revived out-of-band by the operator — useful for judging blast radius before calling.

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?

Two sentences, zero padding, and the action statement is front-loaded ahead of the consequence note. Every clause contributes.

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

Completeness4/5

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

For a two-parameter mutation with full schema coverage and no output schema, this is nearly complete: action, target, and irreversibility are all conveyed. Minor gap — it doesn't say what happens if the container is already stopped or missing (error vs. no-op).

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 both `name` (required) and `server` documented inline, so the schema carries the load. The description adds nothing about parameter handling — e.g. whether `name` must be exact, or how `server` changes targeting — so baseline 3 applies.

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?

States a specific verb and resource ("Stop a Docker container") plus the addressing key ("by name"), which distinguishes it cleanly from siblings like docker_restart, docker_list, and docker_logs. An agent can select it from the tool list without opening the schema.

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 clarifies the terminal nature of the action but never names the obvious alternative: docker_restart exists and is the right call when the container should come back up. Usage is implied rather than routed, leaving the stop-vs-restart decision to inference.

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