omv-mcp

by vnaveenb

Overview Schema Source Related Servers Discussions Admin

Python

Local

docker_exec

Destructive

Execute shell commands inside a Docker container as its user, capturing stdout, stderr, and exit code.

Instructions

Run a shell command inside a container as its user. UNRESTRICTED -- no allow/deny-list. Returns {stdout, stderr, exit_code}.

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>",
      "cmd": "<cmd>"
    },
    "name": "docker_exec"
  }
}

Input Schema

Name	Required	Description	Default
`cmd`	Yes
`name`	Yes
`timeout`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds critical context beyond that: it explicitly states 'UNRESTRICTED -- no allow/deny-list,' clearly warning about the lack of safety filters. It also discloses the execution context ('as its user') and return format ('{stdout, stderr, exit_code}'), which are useful behavioral traits.

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?

The description is a single, well-structured sentence followed by a critical warning and return info. It is front-loaded with the core purpose, uses caps for emphasis, and contains no unnecessary words.

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 simple tool with 3 params and no output schema, the description covers the main purpose, safety warning, and return format. However, it lacks explicit parameter semantics and usage guidance, and the low schema coverage leaves the agent to infer important details like container name vs ID and timeout units.

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?

Schema description coverage is 0%, so the description must compensate. It implicitly indicates that 'cmd' is a shell command and 'name' is the container, but it does not explicitly define the parameters or explain 'timeout' (e.g., units). No additional format or validation details are provided, leaving gaps 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 the tool's function: 'Run a shell command inside a container as its user.' It uses a specific verb ('Run'), identifies the resource ('container'), and distinguishes itself from sibling tools like 'run_command' by specifying the execution context. The 'UNRESTRICTED' warning adds important scope.

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 conveys that the tool is unrestricted ('no allow/deny-list') and executes as the container user, implying it is the go-to for arbitrary container commands. However, it does not explicitly state when to use it over alternatives (e.g., 'run_command' for host commands) or provide exclusion criteria.

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