Skip to main content
Glama
MCP Dokploy Online
by igoruam

settings-getUpdateData

Idempotent

Fetches Dokploy update data from your instance's settings to help you check release status and plan upgrades.

Instructions

POST /settings.getUpdateData

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": "settings-getUpdateData"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

The annotations already disclose openWorldHint=true and idempotentHint=true; the description adds nothing beyond repeating the HTTP method. It does not say whether the call is safe, whether it requires credentials, what it fetches, or why a POST is idempotent, so no behavioral context is contributed.

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 shortness here reflects under-specification rather than economy: one line that conveys an endpoint path and nothing an agent can act on. No wasted words, but no useful words either.

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?

Even for a zero-parameter tool, the description leaves the agent unable to predict what the call returns or whether it should be invoked at all, and there is no output schema to compensate. With openWorldHint=true signaling an external network call, the absence of any explanation of the retrieved data is a serious gap.

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 no parameters, so there is nothing for the description to clarify; baseline 4 applies. The empty schema fully covers the argument surface.

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?

"POST /settings.getUpdateData" only restates the tool name in HTTP form; it never says what the tool actually does or what data it concerns (update availability? settings update payload?). An agent cannot distinguish it semantically from the many sibling settings-* tools, and the verb 'get' paired with a POST adds ambiguity rather than clarity.

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 explanation of when this is preferable to settings-getDokployVersion or the various settings-update* tools, and no prerequisites or exclusions. The description provides zero routing information.

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