ncloud-gov-mcp-server

ncloud_dns_list_records

Read-only

Fetch DNS records associated with a specific domain ID. Supports pagination, record type filter, and content search for efficient management.

Instructions

List DNS records for a specific Global DNS domain with pagination

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

Input Schema

Name	Required	Description
`page`	Yes	Page number (0-based)
`size`	Yes	Number of items per page
`domainId`	Yes	Domain ID to list records for
`recordType`	No	Filter by record type
`searchContent`	No	Search filter for record content

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The annotations provide readOnlyHint=true and the description confirms a read-only list operation with pagination. It adds minimal context about pagination behavior, but does not disclose edge cases like invalid domainId handling or result ordering. This is a modest addition beyond annotations, not a contradiction.

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 conveying the action, resource, scope, and pagination feature. Every word earns its place and there is no redundant content.

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 simple read-only list tool with a well-documented schema, the description plus schema provide sufficient information to invoke correctly. However, the optional recordType and searchContent filters are not mentioned in the description, and there is no indication of response format, leaving a small gap.

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 has 100% description coverage for all five parameters, including domainId, page, size, recordType, and searchContent. The description adds no extra parameter semantics beyond what the schema already documents; it only mentions pagination, which is already evident from the required page and size params. Baseline 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 uses the specific verb 'List' with the resource 'DNS records' and scopes it 'for a specific Global DNS domain' plus mentions pagination. This clearly distinguishes it from sibling tools like ncloud_dns_list_domains (lists domains) and ncloud_dns_create_records (creates records).

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 description implies this tool is used to list DNS records for a Global DNS domain, but it does not explicitly state when to use it versus alternatives such as ncloud_dns_list_lb_records. There is no mention of prerequisites or exclusions, so usage guidance is only implied.

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

Deploy Server