Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-testConnection

Idempotent

Verify connectivity to a DNS provider by testing its configuration. Use this to confirm credentials and network access before deploying DNS records.

Instructions

POST /dnsProvider.testConnection

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": "dnsProvider-testConnection"
  }
}

Input Schema

NameRequiredDescriptionDefault
configNo
dnsProviderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations carry the full behavioral load here (openWorldHint=true for an outbound DNS provider call, idempotentHint=true), and the description adds nothing beyond them — no mention of credentials being used, error modes, timeouts, or whether a failed test mutates any stored state. For a network-touching tool with two undocumented inputs, this is a pure restatement.

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 is under-specification rather than conciseness; the single token line is not front-loaded information an agent can act on. Nothing is wasted because nothing is said.

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 tool that reaches an external DNS provider with an opaque `config` object and an optional provider ID, and with no output schema to explain results, the description provides no completeness at all. An agent cannot predict what a successful or failed test returns.

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% and the description supplies no parameter meaning whatsoever. Whether `dnsProviderId` refers to an existing stored provider versus whether `config` is an inline credential override — a critical distinction, since all params are optional — is left entirely unresolved.

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 entire description is "POST /dnsProvider.testConnection" — it restates the tool name in HTTP terms rather than stating what testing the connection actually does or verifies (credentials? reachability? zone access?). The POST verb does hint that the call may have side effects, but the purpose remains a tautology of the name.

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 usage context at all: nothing says when to call this versus verifying a provider another way, whether the provider must already exist, or what a caller should do with the result. The agent must infer everything 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