Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-assignToProject

Idempotent

Assigns an existing tag to a specific project in Dokploy by submitting project and tag IDs, so projects can be organized and filtered by tag.

Instructions

POST /tag.assignToProject

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

Input Schema

NameRequiredDescriptionDefault
tagIdYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already supply openWorldHint=true and idempotentHint=true, so the safety/repeatability profile is covered structurally. The description adds nothing beyond the endpoint string — no statement of what happens on re-assignment, authorization requirements, or effects on the project/tag state.

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 technically terse, but the brevity is under-specification rather than efficiency: the single line conveys no information an agent could act on beyond the endpoint path. There is no front-loaded statement of purpose.

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 mutation endpoint with zero documented parameters, no output schema, and only sparse annotations, the description leaves essentially everything an agent needs unanswered. It is inadequate relative to the tool's complexity.

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 two required parameters (tagId, projectId), and the description supplies no meaning, format, or constraint information to compensate. Only the parameter names themselves carry semantics.

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 only "POST /tag.assignToProject", which restates the tool name and HTTP verb rather than stating in plain terms that it attaches an existing tag to a project. The POST verb does hint at a mutation, but no resource relationship or effect is described.

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 at all: nothing distinguishes this from sibling tag-bulkAssign, tag-removeFromProject, or tag-create. The agent must infer the choice purely from the tool 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