Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-create

Create a tag in Dokploy by providing a required name and optional color, so you can organize and label deployments or resources consistently.

Instructions

POST /tag.create

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>"
    },
    "name": "tag-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
colorNo

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 supply only openWorldHint=true and a title; the safety profile (mutation, reversibility) is not declared, so the description carries the full burden and delivers nothing. It does not say whether names must be unique, what happens on duplicate names, what is returned (e.g., the new tag's id), or what permissions are required.

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 the brevity is under-specification rather than concision — a single route string that conveys no information beyond the tool name. There is no front-loaded statement of action or scope.

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?

For a mutating, open-world create tool with two undocumented parameters, no output schema, and near-empty annotations, the definition provides nothing an agent needs to call it correctly or predict its effects.

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% for both parameters, so the description must compensate and does not. It never mentions the required name or the optional nullable color, nor any format, length, or uniqueness constraints beyond what the bare JSON schema types show.

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.create" only restates the tool name and HTTP verb; it is a route echo rather than a statement of purpose. It implies creation of a tag but never says what a tag is in this system or what creating one affects.

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?

No guidance at all on when to use this versus siblings such as tag-update, tag-assignToProject, or tag-bulkAssign. Nothing indicates prerequisites, or that the tag must then be assigned separately before it has any effect.

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