Skip to main content
Glama
MCP Dokploy Online
by igoruam

licenseKey-updateEnterpriseSettings

Idempotent

Enable or disable enterprise features for a Dokploy license key by updating its settings.

Instructions

POST /licenseKey.updateEnterpriseSettings

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

Input Schema

NameRequiredDescriptionDefault
enableEnterpriseFeaturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and idempotentHint=true, but the description adds nothing beyond a bare POST path — it does not say whether the change is reversible, what permissions or a valid license key are required, or what happens when the flag is toggled. A mutation tool with no destructiveHint and no explanation leaves the agent guessing about impact.

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 comes from under-specification rather than efficiency; a bare route string is not a useful description and contains no front-loaded purpose statement.

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?

For a settings-mutating tool with an undocumented boolean flag, no output schema, and only sparse annotations, the definition is far too thin — an agent cannot determine effect, scope, or return behavior.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single parameter enableEnterpriseFeatures, and the description does not compensate at all — it never names the parameter, its default, or what enabling it entails. This is exactly the low-coverage case where the description must carry meaning and fails to.

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 HTTP route 'POST /licenseKey.updateEnterpriseSettings', which restates the tool name and HTTP verb rather than explaining what settings are changed or what enabling enterprise features means. An agent can infer a mutation on license/enterprise settings from the name alone, so the text adds no distinguishing information versus siblings like licenseKey-getEnterpriseSettings.

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 when-to-use guidance, no prerequisites, and no mention of the obvious alternative licenseKey-getEnterpriseSettings or of licenseKey-activate/validate. The agent must guess the context entirely.

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