Skip to main content
Glama
Sign In
cargoshipper-mcp

cargoshipper-mcp

by scarr7981
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

docker_stop_container

Stop a running Docker container by providing its container ID or name, with an optional timeout for forceful termination.

Instructions

Stop a Docker container

Args: container_id: Container ID or name timeout: Timeout in seconds before forcefully killing

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

Input Schema

NameRequiredDescriptionDefault
container_idYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Mentions timeout for forceful killing, but does not disclose behavioral traits like what happens on success, if container already stopped, or effects on attached processes. No annotations are present.

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?

Extremely concise: two sentences plus an Args block. No wasted words; every part contributes to clarity.

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?

Adequate for a simple stop action, but lacks details on output or edge cases. Given the presence of an output schema, the description does not need to explain return values, but could mention transition to stopped state.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description adds meaning beyond the schema: container_id is 'Container ID or name' and timeout is 'seconds before forcefully killing'. This is helpful for an agent.

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 'Stop a Docker container', using a specific verb and resource. It distinguishes itself from siblings like docker_remove_container (which removes) and docker_start_container (which starts).

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 tool versus alternatives such as docker_remove_container or docker_kill. The description lacks context for appropriate usage scenarios.

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