Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-generateToken

Idempotent

Creates a new API token for a Dokploy user account, enabling authenticated access to deployment and infrastructure management endpoints.

Instructions

POST /user.generateToken

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds nothing beyond the annotations: no statement about whether a new token invalidates prior tokens, whether the token is returned once, or its lifetime. For a credential-minting operation that is a meaningful omission.

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?

One short line with no waste, but its brevity comes from under-specification rather than economy. It is neither front-loaded with intent nor structured to help an agent decide anything.

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?

No output schema and no parameters, so the description carries the full burden of explaining what is returned and when to call it, and it says nothing. Even the return payload of a token-generation call, which an agent must handle to use the tool, is entirely undocumented.

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 no parameter meaning to convey and the schema is trivially complete. Nothing in the description is needed on this dimension.

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 only restates the tool name as an HTTP path ("POST /user.generateToken"), giving a verb and resource but no explanation of what a token is for, its scope, or how it differs from scim-generateToken or user-getMetricsToken. This is effectively tautological.

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 at all. It does not say which token flavors exist, whether this is for API keys, sessions, or metrics, nor any prerequisite such as authentication or permissions. Several sibling token tools exist and the description provides no basis for choosing among them.

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