infra-ops-mcp

docker_container_start

Start a stopped Docker container, requiring confirmation to safely resume operations.

Instructions

[DANGEROUS] Start a stopped Docker container

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": {
      "containerId": "<containerId>",
      "confirm": "<confirm>"
    },
    "name": "docker_container_start"
  }
}

Input Schema

Name	Required	Description	Default
`containerId`	Yes
`confirm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided; the description only adds a danger tag but fails to disclose requirements (confirm boolean), failure scenarios, or side effects like starting dependencies or network changes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence is concise but lacks necessary detail; the 'DANGEROUS' tag adds emphasis but doesn't replace missing structural elements.

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?

With no output schema, no annotations, and no parameter explanations, the description fails to provide a complete understanding of the tool's behavior and return values.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain either parameter (containerId or confirm), leaving the agent without semantic context for proper usage.

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 the action ('Start a stopped Docker container') and the resource, distinguishing it from siblings like stop, restart, and inspect.

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 vs. alternatives, no mention of prerequisites or conditions (e.g., container must be stopped), and the 'confirm' parameter is not explained.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server