Skip to main content
Glama
Sign In
daimonos

daimonos

by beardfaceguy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

docker

Perform container and image management using commands for listing, logging, executing, inspecting, stopping, and compose operations.

Instructions

Docker operations. Commands: ps, logs, exec, images, inspect, stop, compose_up, compose_down, compose_ps.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior1/5

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

No annotations are present, so the description must disclose behaviors. The description lists commands such as 'stop' (destructive) but does not explain side effects, permissions needed, or whether operations are safe. The tool's behavior is opaque, and the lack of parameters makes invocation unclear.

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

Conciseness2/5

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

The description is short but poorly structured. The phrase 'Docker operations' is redundant with the tool name, and the comma-separated command list lacks hierarchy or explanation. Critical information is missing, making the text underspecified rather than concise.

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

Completeness1/5

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

Given the complexity of Docker operations (multiple sub-commands), the empty input schema, and lack of output schema, the description is highly inadequate. An agent cannot determine how to invoke specific commands, handle errors, or interpret results. The description fails to provide necessary context for a tool with zero parameters and no annotations.

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

Parameters2/5

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

The input schema is empty (no parameters), and schema coverage is 100%. Basline is 3, but the description does not explain how to specify which Docker command to run. It adds a list of commands but fails to map them to any input, leaving the agent without guidance on invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Docker operations' and lists commands like ps, logs, exec, etc. However, the tool name 'docker' is already broad, and the description does not clarify the tool's specific role or how it differs from a general Docker CLI. The purpose is vague and restates the name with minimal addition.

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 is provided on when to use this tool vs alternatives. Sibling tools include 'exec' and 'batch', but there is no mention of choosing this tool over them or any prerequisites. The description lacks explicit context for usage.

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