Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-haveValidLicenseKey

Read-onlyIdempotent

Checks whether a Dokploy instance has a valid license key, helping you verify licensing status before deployment or configuration.

Instructions

GET /licenseKey.haveValidLicenseKey

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

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 readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so safety and retry behavior are covered by structured data. The description adds nothing beyond that – no note on whether the check hits a remote license server (relevant given openWorldHint), no caching or rate-limit behavior, and no indication of what a negative result means.

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 line with no wasted words, but that brevity comes from under-specification rather than tight writing. There is no structure beyond the endpoint path.

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?

With no output schema and no parameters, the description is the only source of information about the result, yet it never says the tool returns a boolean validity flag or what determines validity. For a zero-arg predicate tool this is a meaningful gap, though the low complexity keeps it from being severe.

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 no parameter semantics to explain; the baseline of 4 applies. The empty schema is consistent with the description.

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 string "GET /licenseKey.haveValidLicenseKey", which restates the tool name rather than explaining it in prose. An agent can guess this checks whether a license key is valid, but nothing states the semantics (what validity means, what inputs are implied, e.g. an ambient stored key). It does not distinguish this from the sibling 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 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 exclusion criteria, and no mention of the closely related licenseKey-validate or licenseKey-activate siblings. Any routing decision must be inferred entirely from the name.

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