Skip to main content
Glama

devops-linux

docker_run_to_compose

Translate a docker run command into a clean docker-compose.yml service definition preserving ports, volumes, env vars, restart policy, and networks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "docker_run_to_compose"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNodocker run command line.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Translate' plus the list of preserved attributes (ports, volumes, env vars, restart policy, networks) implies a non-executing, pure-format transformation, which is useful signal, but it never states that Docker is not invoked, does not describe the returned artifact's format, and says nothing about behavior for unsupported or ambiguous flags.

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?

A single front-loaded sentence with a clear verb-first structure and no filler. It is tightly sized for a one-parameter tool; the only shortfall is that terseness comes at the cost of the behavioral and output details noted elsewhere.

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 one-parameter translation tool with no output schema, the description should at least indicate that the result is a compose YAML snippet returned as text and that unsupported flags may be dropped or rejected. It covers scope well but leaves the output and failure behavior unspecified, which an agent needs since no output schema exists.

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?

Only one parameter exists and schema coverage is 100%, so the schema already documents 'text' as the docker run command line. The description adds the useful framing that the whole command line (including the enumerated resource flags) is what gets parsed, but no syntax, quoting, or multi-line guidance 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?

Uses a specific verb ('Translate') and names both the source ('docker run command') and target ('docker-compose.yml service definition'), plus enumerates what is preserved. An agent can tell this is a conversion tool, though it does not explicitly distinguish itself from the nearest sibling docker_to_systemd beyond the target format.

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?

Usage is implied by the source/target pair (use it when you have a docker run string and want a compose file). There is no explicit when-to-use trigger, no statement of when not to use it, and no pointer to docker_to_systemd as the alternative for systemd output.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources