Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-getUserByToken

Read-onlyIdempotent

Retrieves the user account associated with a given token. Use it to identify which Dokploy user a token belongs to before performing account-specific operations.

Instructions

GET /user.getUserByToken

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": {
      "token": "<token>"
    },
    "name": "user-getUserByToken"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

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 declare readOnlyHint, idempotentHint and openWorldHint=true, so the safety profile is covered without the description. The description contributes nothing further: no note on invalid/expired token behavior, whether it returns the token's owner, or whether it has side effects like token extension, despite openWorldHint implying external lookups.

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 brevity here is under-specification rather than concision; the single line is a route annotation, not an explanatory sentence, and leaves no front-loaded statement of purpose for the agent to anchor on.

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?

With no output schema, no parameter documentation and no annotations explaining return behavior, the definition leaves almost everything unknown: return shape, unknown-token handling, and relationship to user-get are all unaddressed. For a lookup tool that an agent must call with an exact token, this is materially incomplete.

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?

The single required parameter 'token' has 0% schema description coverage, so the entire burden falls on the description and it says nothing. It does not distinguish a session token, API key, or metrics token, nor state a format or validation rule beyond the schema's minLength:1.

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 HTTP verb plus the endpoint name, 'GET /user.getUserByToken', which restates the tool name rather than explaining what the operation does. It implies fetching a user record from a token, but never says so in words or defines what kind of token is accepted.

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. Siblings such as user-get, user-getMetricsToken, user-generateToken and application-refreshToken clearly overlap in the token/user-retrieval space, and the description offers no rule for choosing among them or any prerequisite for calling this one.

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