Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-update

Idempotent

Update an existing Dokploy tag by ID, including its name and color, to keep labels accurate.

Instructions

POST /tag.update

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": {
      "tagId": "<tagId>"
    },
    "name": "tag-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
colorNo
tagIdYes
createdAtNo
organizationIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare idempotentHint=true and openWorldHint=true, but the description adds nothing about what is mutated, which fields are overwritten versus left untouched, or what permissions are required. For a mutation endpoint, this is a complete absence of behavioral disclosure.

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 text is short, but this is under-specification rather than conciseness — a bare route string with no front-loaded statement of purpose. Nothing here earns its place because nothing informative is conveyed.

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?

A mutation tool with five undocumented parameters, no output schema, and no destructive/partial-update semantics explained is far from complete. An agent would be guessing at what a call actually changes.

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% across five parameters, so the description carries the full burden, yet it says nothing about tagId, name, color, createdAt, or organizationId. It is impossible to know from the text whether createdAt or organizationId are writable or read-only echoes.

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?

"POST /tag.update" only restates the tool name and its HTTP route; it never says in plain language that an existing tag's properties (name, color) are modified. No sibling is differentiated, so an agent cannot tell it apart from tag-create or tag-assignToProject from the text alone.

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 prerequisite (e.g. tag must already exist), and no mention of the many tag-* alternatives such as tag-create or tag-remove. The agent must infer everything 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