Skip to main content
Glama
MCP Dokploy Online
by igoruam

user-revokeSession

Idempotent

Revoke an active Dokploy user session by session ID to terminate access and invalidate the session. Use it to sign out a specific session or cut off unauthorized access.

Instructions

POST /user.revokeSession

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": {
      "sessionId": "<sessionId>"
    },
    "name": "user-revokeSession"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

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 idempotentHint=true and openWorldHint=true, so the description has a lower bar, yet it adds nothing: it does not say whether the session is invalidated immediately, whether the target user is logged out, what happens if the sessionId is unknown, or what authorization is required. The only signal (POST implies a write) is derived from the route string, not from explanatory text.

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?

The text is short, but it is a route fragment rather than a front-loaded explanation, so there is no structure to speak of and no information value per sentence.

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?

For a destructive-ish mutation with no output schema, thin annotations, and an undocumented required identifier, the description leaves every question an agent would have unanswered. It is inadequate relative to the tool's complexity.

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% for the single required parameter sessionId, and the description provides no compensating information about whether this is an internal session identifier (as returned by user-listSessions) or a token, nor its format. The description does nothing to resolve that ambiguity.

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 route "POST /user.revokeSession", which restates the tool name rather than explaining what revoking a session does. An agent can infer a mutation on a session resource, but nothing distinguishes this from siblings like user-listSessions or user-session beyond the verb in the name.

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 escalation to an alternative, and no statement of prerequisites. Candidate siblings (user-listSessions, user-session, user-one) are never mentioned or contrasted.

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