ncloud-gov-mcp-server

ncloud_list_cache_backup_details

Read-only

Retrieve detailed backup information, including file paths, for a Cloud Cache server instance by providing the Cloud Cache and server instance numbers.

Instructions

List detailed backup information for a Cloud Cache server instance (includes file paths)

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": {
      "cloudCacheInstanceNo": "<cloudCacheInstanceNo>",
      "cloudCacheServerInstanceNo": "<cloudCacheServerInstanceNo>"
    },
    "name": "ncloud_list_cache_backup_details"
  }
}

Input Schema

Name	Required	Description	Default
`cloudCacheInstanceNo`	Yes	Cloud Cache instance number
`cloudCacheServerInstanceNo`	Yes	Cloud Cache server instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description's 'List' is consistent with that. The description adds the behavioral detail that results include file paths, which is useful context, but does not disclose other traits like pagination or return format. With annotations covering the safety profile, this is a moderate score.

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 that conveys the action, target, and a key detail (file paths) without any filler or redundancy. It is perfectly concise.

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?

The tool is simple with two required parameters and a read-only annotation. The description covers the core purpose and an important output detail. It doesn't explain relationships to sibling list tools or edge cases, but given the low complexity and good annotations, it is reasonably 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 documents both parameters with descriptions, giving 100% schema coverage. The description references a 'Cloud Cache server instance' which aligns with the parameter names, but it doesn't add meaning beyond the schema's parameter descriptions. Baseline 3 is appropriate.

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 clearly states the action (List) and resource (detailed backup information for a Cloud Cache server instance), and adds the specific detail 'includes file paths' to indicate granularity. However, it does not explicitly differentiate from sibling tools like ncloud_list_cache_backups, so it earns a 4 rather than a 5.

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 when to use this tool (when detailed backup info with file paths is needed) but does not explicitly mention alternatives or when not to use it. This is adequate but not fully explicit.

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

Deploy Server