Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-one

Read-onlyIdempotent

Retrieve a single Dokploy tag by its ID to inspect tag details and verify configuration.

Instructions

GET /tag.one

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-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered structurally. The description contributes nothing on behavior — not whether missing tags error or return empty, not what the response shape is, not whether it is paginated or rate-limited.

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 not concise in any useful sense — it is a bare endpoint label rather than a front-loaded explanation. Under-specification, not economy of words.

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

Completeness2/5

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

For a one-parameter read tool with annotations covering safety, the structured fields do most of the work, but the description leaves the identifier semantics and return expectations entirely unaddressed. Something like "Fetch a single tag by its id; use tag-all to list tags" would close the gap.

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

Parameters2/5

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

There is one required parameter, tagId, whose schema has 0% description coverage. The description does not clarify the expected identifier format (opaque id vs name vs slug) or whether it must reference an existing tag.

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?

"GET /tag.one" is an HTTP route restatement that only weakly signals intent: GET implies a read and "one" implies a single resource, but the tool's name already conveys both. It never says what a tag is or what fields the fetched object contains.

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

Usage Guidelines2/5

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

No guidance on when to call this versus list-style siblings such as tag-all or tag-update. The agent must infer that a single tag id is required and that this is the retrieval path.

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