Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_cache_manual_backups

Read-only

List all manual backups for Cloud DB for Cache in a specified region to track available restore points. Use this to get an overview of manual backups without filtering by instance.

Instructions

List manual backups for Cloud DB for Cache in the region. This API takes no instance filter or pagination — use ncloud_list_cache_manual_backup_details for one instance's backups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g., KR, JPN, SGN)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.15.0
    • removedInput schema / properties / cloudCacheInstanceNo
      Removed value: -{
-  "description": "Filter by Cloud Cache instance number",
-  "type": "string"
-}
    • removedInput schema / properties / pageNo
      Removed value: -{
-  "description": "Page number for pagination",
-  "type": "number"
-}
    • removedInput schema / properties / pageSize
      Removed value: -{
-  "description": "Page size for pagination",
-  "type": "number"
-}
    • addedInput schema / properties / regionCode
      Added value: +{
+  "description": "Region code (e.g., KR, JPN, SGN)",
+  "type": "string"
+}
  2. First observedv1.10.1

TDQS

A4.4/5.0
Behavior4/5

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

The readOnlyHint annotation already covers safety, and the description adds behavioral context beyond it: the call is region-scoped, has no instance filter, and does not paginate. It does not describe return format, but for a straightforward list operation the disclosed constraints are the most important behavior.

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?

Two sentences with no filler: the first states the action and scope, the second states limitations and routes to the sibling tool. All information is front-loaded and useful.

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 a simple one-optional-parameter list with readOnlyHint set, so the description is largely complete: it names the resource, scope, constraints, and the relevant alternative. It could mention the sibling ncloud_list_cache_backups for automatic/overall backups or describe the response shape, but neither is essential for an agent to invoke it correctly.

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%, with regionCode already explained as a region code with examples. The description's phrase 'in the region' merely echoes the parameter rather than adding new syntax, format, or default behavior, so the schema baseline of 3 applies.

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 and resource ('List manual backups for Cloud DB for Cache in the region') and explicitly differentiates from ncloud_list_cache_manual_backup_details. It also conveys the aggregate scope ('no instance filter') so an agent can distinguish it from nearby cache tools.

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

Usage Guidelines5/5

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

It states the API's constraints ('takes no instance filter or pagination') and gives an explicit alternative with the condition for choosing it ('use ncloud_list_cache_manual_backup_details for one instance's backups'). This is clear when-to-use guidance, not merely an implied context.

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