ncloud-gov-mcp-server

ncloud_dns_update_records

Idempotent

Update DNS records for a specific Global DNS domain by providing record IDs and new values for host, type, content, and TTL.

Instructions

Update DNS records for a specific Global DNS domain

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": {
      "domainId": "<domainId>",
      "records": "<records>"
    },
    "name": "ncloud_dns_update_records"
  }
}

Input Schema

Name	Required	Description	Default
`records`	Yes	Array of DNS records to update
`domainId`	Yes	Domain ID to update records for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations (idempotentHint: true, destructiveHint: false) already indicate safety for retries and non-destructive behavior. The description adds no additional behavioral context, such as whether the operation replaces the entire record set or updates individual records, but 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.

Conciseness5/5

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

The description is a single, front-loaded sentence that conveys the essential action without redundant words. It is appropriately concise and free of filler.

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 simple update tool, the description is minimally sufficient given the rich schema and annotations. However, it omits important context such as the need to obtain existing record IDs (e.g., via list_records) and whether the records array replaces or patches existing entries. This could lead to incorrect invocation without additional research.

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?

The input schema provides complete descriptions for both parameters (domainId and records), including nested record fields. The description adds no extra semantic value beyond what the schema already documents, so the baseline score of 3 is appropriate.

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 clearly states the action ('Update') and resource ('DNS records') for a specific domain. However, it does not explicitly differentiate from the sibling tools ncloud_dns_create_records and ncloud_dns_delete_records, though the verb 'update' implies modification of existing records.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like create or delete records. It does not mention prerequisites (e.g., needing existing record IDs) or scenarios where this tool is appropriate, leaving the agent to infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server