Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List Dns Records

listDnsRecords
Read-only

Retrieve DNS records for a Cloady-registered domain or an application's cloady.io address to inspect A, AAAA, wildcard, and managed records.

Instructions

The DNS records of a domain registered through Cloady in this workspace, or of an application's own address under cloady.io (<app>-<hash>-<workspace>.cloady.io, as its endpoints show it). A registration starts with A and AAAA records for the domain and * pointing at Cloady; an address starts with none, since a wildcard serves it. Records with managed set are Cloady's: they keep the domain or address pointing at your applications and can't be changed or deleted. Answers 409 when a registered domain uses its own nameservers, whose records live there.

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": {
      "workspaceSlug": "<workspaceSlug>",
      "domain": "<domain>"
    },
    "name": "listDnsRecords"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior, so the bar is lower, and the description adds materially: records with `managed` set cannot be changed or deleted, defaults differ between registrations (A/AAAA plus `*`) and app addresses (none), and it returns 409 when a registered domain uses external nameservers. These are behavioral facts an agent could not derive from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph with no filler — each sentence carries new information (scope, defaults, immutability, error case). The opening is a noun phrase rather than a verb, which makes it slightly less immediately scannable, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-parameter read-only list tool with no output schema, the description supplies enough: what is returned at a structural level (A/AAAA, wildcard, managed flag), why some records are immutable, and the one failure mode. Only the workspaceSlug parameter and what an empty result means are unaddressed.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry parameter meaning. It does clarify the accepted forms of the domain argument (registered domain vs `<app>-<hash>-<workspace>.cloady.io`), which is the most valuable thing to know, but it never mentions workspaceSlug or explains how the two required parameters interact beyond 'in this workspace'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource precisely — DNS records for either a domain registered in the workspace or an app's own cloady.io address — and gives concrete examples of both, distinguishing the two scopes clearly. It stops short of naming the read action as a verb and doesn't explicitly contrast with createDnsRecord/updateDnsRecord/deleteDnsRecord siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The split between 'domain registered through Cloady' and 'application's own address' implies which identifiers to pass, and the 409 note tells the agent when the call will fail, which is weak but real when-not guidance. There is no explicit routing to alternatives such as listWorkspaceDomains for discovering domains, or createDnsRecord for adding entries.

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