Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Create Tag

createTag

Define a reusable monitor tag with a name and color before attaching it to Uptime Kuma monitors; create tags in advance to avoid duplicates and keep monitor organization consistent.

Instructions

Creates a tag with a name and a color. Tags are attached to monitors with the tags argument of createMonitor / updateMonitor, which also creates a tag that does not exist yet, so this is only needed to define a tag ahead of use. Names are not unique: check listTags first to avoid a duplicate. To rename or recolor a tag use updateTag; to remove one, deleteTag.

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>",
      "color": "<color>"
    },
    "name": "createTag"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTag name
colorYesTag color as a hex string (e.g. "#ff0000") or CSS color name

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo
tagNo

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 already declare the write, non-idempotent, non-destructive profile, and the description adds genuinely new behavior: names are not unique, duplicates are possible, and monitors auto-create missing tags. It does not mention auth/permission requirements, but the output schema covers the response shape, so the remaining gap is small.

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 tight sentences, front-loaded with the action, then the relationship to createMonitor/updateMonitor, then the duplicate caveat, then the sibling routing. Every sentence carries distinct information with no repetition of the schema.

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?

For a two-parameter create tool with full annotation coverage and an output schema, the description supplies everything an agent needs: purpose, prerequisite check, duplicate risk, and the correct sibling for follow-up operations.

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% and already documents both parameters including the hex/CSS color format, so the baseline is 3. The description adds real semantic meaning beyond the schema by stating that name is not a unique key, which changes how an agent should choose values.

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 tag with a name and a color") and immediately distinguishes it from the implicit tag creation performed by createMonitor/updateMonitor, so an agent can tell why this tool exists separately from its siblings.

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 ("only needed to define a tag ahead of use"), a pre-check ("check listTags first to avoid a duplicate"), and named alternatives for the adjacent operations (updateTag for rename/recolor, deleteTag for removal). Nothing is left to inference.

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