Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-one

Read-onlyIdempotent

Retrieves a specific Dokploy user by ID so you can inspect account details and manage user-specific deployment access.

Instructions

GET /user.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": {
      "userId": "<userId>"
    },
    "name": "user-one"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the description adds no behavioral context of its own — no failure mode for unknown userIds, no auth requirements, no note on what happens with missing or unauthorized users. It discloses nothing beyond the structured metadata.

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 only because it is under-specified — the single line is a raw route string with no front-loaded statement of purpose. Brevity here reflects missing content rather than efficient writing.

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 and 0% parameter documentation, the description is the only place an agent could learn what this returns and what userId means, and it supplies neither. It is wholly inadequate for correct invocation.

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?

Schema description coverage is 0% and the sole required parameter userId is undocumented anywhere. The description does not say whether userId is a numeric ID, a username, an email, or the special literal "one" implied by the endpoint path.

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 HTTP endpoint "GET /user.one", which restates the tool name rather than stating in plain language what it returns or why. An agent can guess it retrieves a single user entity, but nothing distinguishes it from siblings like user-get or user-listPasskeys.

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 guidance at all about when to use this tool, when not to, or which sibling (user-get, user-all, user-getUserByToken) is the alternative. The agent must infer everything from the name and 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