Skip to main content
Glama
MCP Dokploy Online
by igoruam

tag-all

Read-onlyIdempotent

Retrieves all tags from a Dokploy instance so you can review existing tag data and manage tags through MCP Dokploy Online.

Instructions

GET /tag.all

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tag-all"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already supply the meaningful behavioral profile here (readOnlyHint=true, idempotentHint=true, openWorldHint=true), so the agent knows this is a safe, repeatable read. The description contributes nothing beyond that — no mention of result volume, pagination, or ordering of the returned tag list. Since annotations carry most of the burden for a zero-parameter read, a 3 is fair, but the description adds zero value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single three-word endpoint string with no wasted words and is trivially front-loaded, but its brevity reflects under-specification rather than disciplined writing. It communicates the endpoint mapping, which is the only content it has.

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 simple parameterless read the bar is low, and the annotations cover safety, but the description says nothing about what is returned (a tag collection), whether the result can be large, or how it relates to the sibling tag tools. An agent picking between tag-all, tag-one, and tag-bulkAssign gets no help.

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?

The tool takes no parameters and the schema is an empty object with additionalProperties=false, so there is no parameter semantics for the description to explain. Baseline 4 applies.

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.all" merely restates the tool name as a raw HTTP path; it never says in prose that this lists all tags. An agent can infer a read of all tag resources, but there is no differentiation from siblings such as tag-one or tag-bulkAssign beyond the bare endpoint string.

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 when-to-use guidance whatsoever: nothing says whether this is the way to enumerate tags versus tag-one, nor any prerequisite or context. The agent must infer usage from the name alone.

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