Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Create Docker Host

createDockerHost

Creates a Docker daemon connection for Uptime Kuma Docker monitors via Unix socket or TCP URL; test it first because it is saved without validation.

Instructions

Creates a Docker daemon connection; docker monitors take the returned ID in their docker_host field. Pass dockerType "socket" with a socket path, or "tcp" with a URL such as http://host:2375 (for example a docker-socket-proxy). The connection is saved without being checked, so call testDockerHost first. To change one use updateDockerHost.

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>",
      "dockerType": "<dockerType>",
      "dockerDaemon": "<dockerDaemon>"
    },
    "name": "createDockerHost"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable name for this docker host
dockerTypeYes"socket" for a unix socket path, "tcp" for an HTTP/HTTPS URL
dockerDaemonYesUnix socket path (e.g. /var/run/docker.sock) when dockerType=socket, or TCP URL (e.g. http://docker-proxy:2375) when dockerType=tcp

Output Schema

NameRequiredDescriptionDefault
idNo
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-idempotent, non-destructive write; the description adds the genuinely non-obvious behavior that "The connection is saved without being checked", which explains why testDockerHost must precede it. It also discloses the returned ID's downstream use, though it does not say what happens on duplicate names or on connect failure.

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?

Four short sentences, front-loaded with the action and its downstream effect, then type selection, then the validation caveat, then the update alternative. No filler; the testDockerHost warning is placed where an agent will read it before calling.

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

Completeness5/5

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

With an output schema present, return values need no explanation, yet the description still notes the returned ID's consumer. For a three-required-parameter create tool with full schema coverage, the ordering requirement and the unvalidated-save caveat close the remaining gaps.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds meaning beyond the schema by tying the dockerType enum values to concrete argument forms and giving a real-world example (a docker-socket-proxy URL). This pairing guidance helps the agent populate dockerDaemon correctly for each type.

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?

States a specific verb and resource ("Creates a Docker daemon connection") and immediately adds downstream scope (docker monitors consume the returned ID in docker_host). It also names the sibling it is not (updateDockerHost), so an agent can distinguish create from update without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use branching for dockerType ("socket" with a path vs "tcp" with a URL such as a docker-socket-proxy), plus a prerequisite ("call testDockerHost first") and an explicit alternative ("To change one use updateDockerHost"). When, how, and the alternative are all covered.

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