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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_cache_buckets

Read-only

List Object Storage buckets available for exporting Cloud DB for Cache backups. Identify suitable storage targets for backup export tasks.

Instructions

List Object Storage buckets available for Cloud DB for Cache backup export

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": "ncloud_list_cache_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (KR, KRS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.1/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this a safe read operation, and the description's 'List' aligns with that. No additional behavioral details (e.g., pagination, return format, or prerequisites) are provided, but with annotation coverage, this does not hurt usability.

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?

A single concise sentence that exactly states the tool's function and context. No wasted words or redundant details.

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

Completeness5/5

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

For a simple read-only list operation with one optional parameter and a clear purpose, the description fully covers what an agent needs to know. No output schema is needed, and the annotations provide safety context.

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 fully documents the single parameter 'regionCode' with its description and optional nature (100% schema coverage). The description adds no parameter-specific information, so the 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 ('List') and identifies the resource ('Object Storage buckets') with a clear purpose ('available for Cloud DB for Cache backup export'). This distinguishes it from sibling bucket-list tools like ncloud_list_mysql_buckets or ncloud_hadoop_list_buckets.

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 context is clearly implied by the purpose: use this tool when you need Object Storage buckets for Cloud DB for Cache backup export. It does not explicitly mention alternatives or exclusions, but the scope is specific enough to guide selection among many similar list tools.

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