Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-validate

Idempotent

Validate a Dokploy license key by calling the licenseKey.validate API endpoint, confirming the key is recognized before you rely on it for deployment and infrastructure management.

Instructions

POST /licenseKey.validate

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 agent knows the call may reach an external system and can be retried. The description adds no behavioral context beyond that: nothing about whether a failed validation returns an error or a falsy result, whether it consumes or mutates license state, or whether it requires network reachability to a licensing backend.

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 brevity here is under-specification rather than conciseness — a bare route string with no front-loaded statement of what the tool does or returns. There is effectively no content to structure.

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 mechanically simple (no inputs, no output schema), but for a validation endpoint the agent needs to know what 'valid' means and what the response conveys, and neither is stated. With openWorldHint signalling an external dependency, some note about the remote check would have been expected.

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 correctly declares an empty object with additionalProperties=false, so there is nothing for the description to clarify. Baseline for a parameterless tool 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 just the HTTP route "POST /licenseKey.validate", which restates the tool name rather than explaining what validation entails — format check, signature check, remote licensing-server call, or license-state check. It is not misleading, but it adds nothing an agent could not infer from the name alone, and it does nothing to distinguish it from the sibling licenseKey-haveValidLicenseKey.

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 guidance whatsoever about when to call this versus licenseKey-haveValidLicenseKey, licenseKey-activate, or licenseKey-deactivate. The presence of a near-synonym sibling (haveValidLicenseKey) makes the absence of routing guidance a real selection risk for an agent.

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