ncloud-gov-mcp-server

ncloud_dns_list_domains

Read-only

Retrieve Global DNS domains page by page. Filter by domain name and paginate results to manage DNS domain listings.

Instructions

List Global DNS domains with pagination. Returns Spring Page structure (content, pageable, totalElements).

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": {
      "page": "<page>",
      "size": "<size>"
    },
    "name": "ncloud_dns_list_domains"
  }
}

Input Schema

Name	Required	Description
`page`	Yes	Page number (0-based)
`size`	Yes	Number of items per page
`domainName`	No	Filter by domain name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description adds value beyond the readOnlyHint annotation by specifying the return structure as a Spring Page object with content, pageable, and totalElements. This gives the agent insight into the response format, which is useful for handling output. It does not contradict 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 concise, with two short sentences that front-load the main purpose and then provide return structure details. Every word adds value, with no redundancy or filler.

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 list operation with readOnlyHint annotation and fully described schema parameters, the description provides the essential details: network scope, pagination, and return format. It could optionally mention the domainName filter, but the schema already covers this, so the description is sufficiently complete.

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 covers 100% of parameters with descriptions, including page (0-based), size, and domainName filter. The description's mention of pagination aligns with the page/size parameters but adds no additional meaning beyond the schema, 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.

Purpose5/5

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

The description clearly states the verb 'List' and the resource 'Global DNS domains', which is specific and distinguishes it from sibling tools like ncloud_dns_get_domain_detail and ncloud_dns_create_domain. The mention of pagination further clarifies the operation's scope.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. It only states what the tool does, leaving the agent to infer usage context from the name and schema alone.

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

Deploy Server