Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-deactivate

Idempotent

Deactivates a Dokploy license key to release its activation and free the associated seat or instance for reuse.

Instructions

POST /licenseKey.deactivate

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": "licenseKey-deactivate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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, lowering the bar, yet the description adds nothing beyond the endpoint path. It does not say whether deactivation is reversible, whether it frees a seat, or what state the key ends in — meaningful context an agent would need before mutating a license.

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?

It is a single short line with no wasted words, but it is a bare route string rather than a structured description, so brevity here reflects under-specification more than disciplined writing.

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?

For a zero-parameter mutation with no output schema, the annotations and schema carry nearly all the weight, and the description supplies no behavioral framing at all. An agent cannot tell from this text what effect the call has on the license or what it should expect back.

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 nothing for the description to clarify; schema coverage is 100% and the empty object schema is self-explanatory. Baseline 4 applies.

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 route "POST /licenseKey.deactivate", which essentially restates the tool name in HTTP form. It implies a mutation of a license key but never states what deactivation means or how it differs from sibling licenseKey-validate or licenseKey-activate.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as licenseKey-activate for the inverse operation. The agent must infer entirely from the tool name that this deactivates rather than checks or retrieves a key.

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