Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-listPasskeys

Read-onlyIdempotent

Retrieve all passkeys registered to the authenticated Dokploy user account, enabling you to review and audit the authentication credentials tied to that user.

Instructions

GET /user.listPasskeys

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

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 readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered by structured fields. The description contributes nothing beyond that — no mention of what a passkey record contains, whether listing is scoped to the caller, or what happens with an empty set.

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?

One short line with no wasted words and the resource name is front-loaded. However, its brevity comes from under-specification rather than from disciplined editing, so it is concise without being informative.

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?

The tool is genuinely simple — no parameters, no output schema, read-only annotations — so an agent needs little. Even so, the definition never says what a passkey is in this domain or what the listing returns, leaving the caller to guess the unit of the response.

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 and the schema is closed (additionalProperties: false), so there is no parameter semantics to explain. Baseline 4 applies since the description has no parameters to document.

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 the raw route string "GET /user.listPasskeys", which merely restates the tool name in HTTP form. It implies a read of passkey records but supplies no verb-plus-resource phrasing, no scope, and no differentiation from siblings such as user-listSessions or user-getBookmarkedTemplates.

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, no prerequisites, and no mention of alternatives. An agent must infer entirely from the name that this enumerates passkeys rather than creating, deleting, or fetching a single 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