ncloud-gov-mcp-server

ncloud_list_mssql_backups

Read-only

List backups for a Cloud DB for MSSQL instance using its instance number. Retrieve backup history to support restore and recovery decisions.

Instructions

List backups for a Cloud DB for MSSQL instance

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": {
      "cloudMssqlInstanceNo": "<cloudMssqlInstanceNo>"
    },
    "name": "ncloud_list_mssql_backups"
  }
}

Input Schema

Name	Required	Description	Default
`cloudMssqlInstanceNo`	Yes	Cloud MSSQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description simply restates the operation 'List backups' and adds no behavioral detail such as pagination, return format, or response structure. The readOnlyHint annotation already conveys the safety profile, but the description offers no additional context beyond what the annotation implies.

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 sentence with no filler, front-loading the action and resource. Every word earns its place, making it appropriately concise for a simple list operation.

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?

With no output schema, the description fails to describe what the returned backup list contains or how it is structured. The tool has a small parameter set and a readOnly annotation, but the description still leaves the agent without information about return values or potential limitations.

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 single required parameter cloudMssqlInstanceNo is fully described in the schema as 'Cloud MSSQL instance number', achieving 100% schema description coverage. The description adds no further semantic information about the parameter, so the high schema coverage supports a baseline score of 3.

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

Purpose4/5

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

The description uses the specific verb 'List' and identifies the resource 'backups' for a Cloud DB for MSSQL instance, clearly stating the core operation. However, it does not differentiate from the sibling tool ncloud_list_mssql_backup_details, which could create ambiguity about which backup-related listing tool to invoke.

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. There is no mention of ncloud_list_mssql_backup_details or any exclusions, prerequisites, or scenarios that would help an agent select this tool over others.

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

Deploy Server