Skip to main content
Glama
MCP Dokploy Online
by igoruam

docker-getEvents

Read-onlyIdempotent

Retrieve Docker events for a specified server over a chosen time window to diagnose container activity and troubleshoot deployment issues.

Instructions

GET /docker.getEvents

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

Input Schema

NameRequiredDescriptionDefault
minutesNo
serverIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered without the description. The description adds nothing beyond that — no note on whether this is a snapshot versus a stream, how many events come back, or whether the result is bounded by the minutes window.

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?

It is short, but this is under-specification rather than conciseness: a bare route string with no sentence structure or front-loaded intent. There is nothing to trim because nothing informative was written.

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 two undocumented parameters, no output schema, and an ambiguous resource name, the definition should explain the events concept, the time window, and the server targeting. None of that is present, leaving the definition insufficient for correct invocation.

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 supplies no parameter meaning at all. The agent is left to guess that "minutes" (default 15, max 1440) is a lookback window and that "serverId" selects a Docker host — neither is stated anywhere.

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 is just the HTTP route "GET /docker.getEvents", which restates the tool name without explaining what an "event" is or what the tool returns. An agent can infer it reads Docker events, but nothing distinguishes it from sibling readers like docker-getContainers or docker-getServerHealth beyond the word "Events".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no mention of alternatives such as container/stack listing tools, and no statement of what the events stream is useful for. The agent must guess entirely from the name.

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