Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-update

Idempotent

Update an existing DNS provider's name and configuration in Dokploy using its provider ID to keep DNS settings current.

Instructions

POST /dnsProvider.update

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dnsProviderId": "<dnsProviderId>",
      "name": "<name>",
      "config": "<config>"
    },
    "name": "dnsProvider-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
configYes
dnsProviderIdYes

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 idempotentHint=true and openWorldHint=true, so the description adds no behavioral context beyond the HTTP verb. It does not say whether the update replaces or merges config, whether existing records are affected, or what permissions are needed — and it does not contradict the annotations.

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 that brevity reflects under-specification rather than economy; a bare route string conveys no front-loaded intent or scope.

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 three-parameter mutation tool with no output schema and no parameter documentation, the definition supplies nothing an agent needs to call it correctly, such as replacement semantics for config or required permissions.

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?

All three required parameters (dnsProviderId, name, config) have 0% schema description coverage, and the description adds nothing about their meaning or format. The opaque 'config' free-form object is especially undocumented in both places.

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 "POST /dnsProvider.update", which restates the tool name rather than stating what the tool does. An agent can infer it mutates a DNS provider, but nothing distinguishes it from sibling dnsProvider-create or vaultProvider-update beyond the word 'update'.

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 alternatives such as dnsProvider-create or dnsProvider-remove. The agent must guess the intended 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