ncloud-mcp-server

ncloud_dns_create_domain

Create a new Global DNS domain to manage DNS records for your domain name. Specify the domain name and optional comment to set up DNS hosting in Naver Cloud Platform.

Instructions

Create a new 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": {
      "name": "<name>"
    },
    "name": "ncloud_dns_create_domain"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Domain name (e.g., example.com)
`comment`	No	Optional comment for the domain

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.3/5.0

Behavior2/5

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

The only annotation is destructiveHint=false, and the description does not contradict that. However, the description discloses no additional behavioral traits: it does not mention that the created domain might need activation/apply, what state it enters after creation, or any name constraints beyond the schema. The verb 'Create' implies a mutation but adds little beyond the annotation.

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 with zero filler. It immediately states the action and resource, making it highly concise and well-structured.

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 2-parameter tool with complete schema and no output schema, the description is mostly sufficient. However, it misses workflow context: a newly created Global DNS domain likely needs to be applied (see sibling ncloud_dns_apply_domain) to become effective, yet this is not mentioned. An agent might assume creation alone fully activates the domain.

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 description coverage is 100% – both 'name' and 'comment' have descriptive text. The tool description itself adds no parameter-specific meaning, so it receives the baseline score of 3 for a fully documented schema.

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

Purpose5/5

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

The description clearly states 'Create a new Global DNS domain', which is a specific verb (create) and resource (Global DNS domain). It distinguishes from siblings like ncloud_dns_create_records (records) and ncloud_dns_delete_domain (deletion).

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. It does not mention prerequisites, follow-up steps (e.g., applying the domain via ncloud_dns_apply_domain), or cases where a different tool would be more appropriate. The agent must infer usage solely 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