Skip to main content
Glama
Sign In
Cloady

Cloady

Official
by Cloady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Update Dns Record

updateDnsRecord
Destructive

Updates an existing DNS record's name, type, content, TTL, and priority within a Cloady workspace domain; returns 409 for managed records and requires developer role.

Instructions

Replaces a record's name, type, content, TTL and priority under the same rules as createDnsRecord. Answers 409 for a record Cloady manages. Needs the developer role.

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>",
      "recordId": "<recordId>"
    },
    "name": "updateDnsRecord"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
recordIdYes
requestBodyNoThe JSON request body.
workspaceSlugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a destructive, non-read-only, open-world mutation, so the description's job is to add specifics – and it does: an explicit 409 outcome for provider-managed records and the required developer role. It stops short of describing success response or whether changes are reversible.

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?

Three short sentences, each carrying distinct information (scope, error behavior, auth), with the replacement semantics front-loaded. Only a minor typo ("Cloady") and slight terseness keep it off a 5.

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

Completeness3/5

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

For a nested-body mutation with no output schema and sparse schema descriptions, the definition covers the important edge cases (managed records, role gating) but omits the semantics of the required identifiers and what a successful call returns. Adequate but with real gaps for a destructive operation.

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 only 25%, so the description has to carry weight; it usefully signals full-replacement (PUT-like) semantics by listing every field that gets overwritten, which is real meaning beyond the schema. But workspaceSlug, domain, and recordId remain completely unexplained, and whether fields can be omitted is left ambiguous.

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?

"Replaces a record's name, type, content, TTL and priority" gives a specific verb and enumerates the mutable fields, which clearly separates this from createDnsRecord and deleteDnsRecord. It does not explicitly name those siblings, but the intent is unambiguous.

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?

It references createDnsRecord for the validation rules and flags one condition where the call will not succeed (409 on records Cloudy manages) plus a role prerequisite. However, it never states when to choose this over updateDomain or deleteDnsRecord/createDnsRecord, and the guidance is implied rather than framed as when-to-use.

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