Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-activate

Idempotent

Activates a Dokploy license key by submitting the required key to validate and enable the license on your instance.

Instructions

POST /licenseKey.activate

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": {
      "licenseKey": "<licenseKey>"
    },
    "name": "licenseKey-activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
licenseKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

Annotations only declare openWorldHint=true and idempotentHint=true; there is no readOnlyHint or destructiveHint, so the safety profile of this mutation is undocumented. The description adds nothing about side effects, whether activation is permanent, what happens to a previously active key, or what the response contains.

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 with no wasted words, but this is under-specification rather than conciseness: the entire description is a machine-route string with zero explanatory content for a human or agent reader.

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, no annotation coverage of mutability, and an undocumented parameter, the definition leaves an agent unable to predict the result of activation or recover from failure. Almost everything needed to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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, so the description carries the full burden and provides nothing about the licenseKey format, length, or source. The parameter name is self-explanatory but no meaning is added beyond it.

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 'POST /licenseKey.activate', which restates the tool name in HTTP route form and adds no resource scope or effect. An agent knows it activates a license key but not what activation entails (seat consumption, entitlement grant, expiry) or how it differs from licenseKey-validate.

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 on when to call this versus the closely related siblings licenseKey-validate, licenseKey-haveValidLicenseKey, or licenseKey-deactivate. No prerequisites, no error conditions, no exclusions are stated.

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