ESA MCP Server

create_site_ns_record

Create NS DNS records for websites to specify authoritative name servers for domain resolution.

Instructions

Creates a DNS record for a specific website. Only NS records are supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_site_ns_record"
  }
}

Input Schema

Name	Required	Description
`siteId`	No	The website ID, which can be obtained by calling the [ListSites] operation.
`recordName`	No	The record name.
`ttl`	No	The TTL of the record. Unit: seconds. If the value is 1, the TTL of the record is determined by the system. Default: 1.
`data`	No	The DNS record information. The format of this field varies based on the record type. For more information, see https://www.alibabacloud.com/help/doc-detail/2708761.html
`comment`	No	The comment of the record. The maximum length is 100 characters.
`required`	No
`annotations`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Creates' implies a write/mutation operation, the description doesn't disclose important behavioral traits like authentication requirements, rate limits, whether the operation is idempotent, what happens on conflict, or what the response looks like. For a creation tool with zero annotation coverage, this is a significant gap.

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 perfectly concise with two sentences that each earn their place: the first states the core purpose, the second adds critical constraint information. There's zero waste or redundancy, and the most important information is front-loaded.

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

Completeness2/5

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

For a creation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address what happens after creation, error conditions, authentication requirements, or provide context about the broader DNS management system. The description covers the 'what' but misses the 'how' and 'what happens next' that an agent needs for reliable tool invocation.

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?

With 71% schema description coverage, the schema already documents most parameters well. The description adds no parameter-specific information beyond what's in the schema. The baseline is 3 when schema coverage is high (>80%), but at 71% it's borderline - the description doesn't compensate for the remaining 29% gap, nor does it add meaningful context about parameter relationships or usage patterns.

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 specific action ('Creates a DNS record') and resource ('for a specific website'), and explicitly distinguishes this tool from siblings by specifying 'Only NS records are supported', which differentiates it from other create_site_*_record tools like create_site_a_or_aaaa_record or create_site_cname_record.

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

Usage Guidelines4/5

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

The description provides clear context about when to use this tool ('Only NS records are supported'), which implicitly distinguishes it from other DNS record creation tools. However, it doesn't explicitly mention when NOT to use it or name specific alternatives, though the sibling tool names make the alternatives obvious.

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