Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-listRecords

Read-onlyIdempotent

Retrieve DNS records for a specified provider and zone to inspect current DNS configuration and verify entries before changes.

Instructions

GET /dnsProvider.listRecords

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>",
      "zoneId": "<zoneId>"
    },
    "name": "dnsProvider-listRecords"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYes
dnsProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered by structured data. The description contributes nothing beyond that—no return shape, no pagination behavior, no rate-limit or ordering notes for what is presumably a live external DNS API call.

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?

The single line contains no filler, but its brevity reflects under-specification rather than economy. It is not front-loaded with any actionable information.

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 requiring two identifiers and hitting an external provider with no output schema, the definition supplies no record format, pagination, or failure-mode context. An agent cannot predict what it will get back or how to handle a large zone.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters (dnsProviderId, zoneId), and the description does not mention either of them. The parameter names are somewhat self-explanatory, which prevents a 1, but the description does nothing to compensate for the coverage gap.

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?

"GET /dnsProvider.listRecords" only restates the tool name as an HTTP verb and path. It implies retrieval of DNS records, but gives no scope, filters, or differentiation from siblings like dnsProvider-listZones or dnsProvider-one.

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 exclusion of alternatives, and no mention of prerequisites such as an existing zone. The agent is left to infer everything from the tool 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