Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-getEnterpriseSettings

Read-onlyIdempotent

Retrieves the current enterprise license settings from a Dokploy instance, so administrators can inspect licensing configuration and status.

Instructions

GET /licenseKey.getEnterpriseSettings

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 repetition behavior are covered. The description adds no behavioral context whatsoever—no indication of what settings are returned, whether licensing state or secrets are exposed, or any authorization requirement.

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 a single endpoint string with no wasted words, but it is under-specified rather than concise—there is no front-loaded statement of purpose or outcome. Length is appropriate only because it says almost nothing.

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, the description carries the burden of telling the agent what comes back, and it does not. For a zero-param read of enterprise/license settings, the agent cannot tell whether the response contains license validity, plan tiers, or configuration values.

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 disambiguate and the baseline of 4 applies. No parameter-related omissions exist.

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 HTTP route 'GET /licenseKey.getEnterpriseSettings', which restates the tool name rather than explaining what enterprise settings are retrieved. An agent can infer a read of license/enterprise settings, but nothing distinguishes it from sibling licenseKey-updateEnterpriseSettings or clarifies the resource content.

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?

No when-to-use guidance is offered, no prerequisites, and no mention of alternatives such as licenseKey-haveValidLicenseKey or the update counterpart. The agent must guess the context in which reading enterprise settings matters.

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