Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-getMetricsToken

Read-onlyIdempotent

Retrieves the current user's metrics token from a Dokploy instance so monitoring integrations can authenticate and collect infrastructure metrics.

Instructions

GET /user.getMetricsToken

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": "user-getMetricsToken"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the route: no indication of what the token grants, whether it is per-user or global, whether it expires, or how it should be handled (secrecy, tenancy). For a credential-related read, that silence is a real gap.

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?

It is extremely short and front-loaded, but it is short because it contains almost no information – a bare route fragment rather than a useful sentence. It is not padded, but it also does not earn its place as a description.

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?

With no output schema and no parameters, the description is the only place to explain what calling this endpoint actually returns (a metrics token value?) and how it relates to the other metrics tools. It provides none of that, so the definition is incomplete even for a simple zero-argument tool.

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 zero parameters, so there is nothing for the description to disambiguate beyond its inclusion in the input schema. Baseline of 4 applies when there are no parameters.

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 the raw route string "GET /user.getMetricsToken", which restates the tool name rather than stating what the tool does. It does not explain what a 'metrics token' is or how it differs from sibling tools like user-getContainerMetrics or user-getServerMetrics, leaving the agent to guess from the name alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent gets no signal about whether this should be preferred over user-getUserByToken, user-generateToken, or the sibling metrics endpoints.

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