Skip to main content
Glama
Sign In
ncloud-gov-mcp-server

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_dns_rollback_domain

Destructive

Roll back a Global DNS domain to its previously applied state, discarding all pending changes. Execute with confirm=true.

Instructions

⚠️ Destructive: Rollback a Global DNS domain to the previously applied state. Pending changes will be discarded. Set confirm=true to execute.

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>"
    },
    "name": "ncloud_dns_rollback_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
domainIdYesDomain ID to rollback

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds concrete behavioral details: it warns '⚠️ Destructive', states 'Pending changes will be discarded', and requires 'Set confirm=true to execute.' This clearly discloses the destructive nature, the specific consequence (discarding pending changes), and the confirmation safeguard.

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, well-structured sentence. It front-loads the destructive warning, states the action, and gives the key requirement. No redundant or filler words.

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 rollback tool with two parameters, the description, combined with the schema and annotations, is nearly complete. It covers what the tool does, the side effects, and the confirmation requirement. It could mention prerequisites like the existence of a previously applied state, but this is likely implied by 'previously applied state.' No output schema is needed for a rollback operation.

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%, so the description does not need to add parameter details. The only parameter-related mention is 'Set confirm=true to execute,' which duplicates the confirm parameter's schema description. No additional semantic value beyond the schema is provided, hence the baseline score.

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 a specific verb+resource: 'Rollback a Global DNS domain to the previously applied state' and clearly distinguishes this from sibling tools like ncloud_dns_apply_domain, ncloud_dns_delete_domain, and ncloud_dns_list_domains. It precisely states the action and the target resource.

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 implies when to use: when you want to revert a domain to its last applied state and discard pending changes. This provides clear context, though it does not explicitly name alternative tools or exclusions. The phrase 'Pending changes will be discarded' clarifies the scenario but could be stronger with an explicit 'use when...' statement.

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

Deploy Server

Other Tools