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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_mongodb_buckets

Read-only

List Object Storage buckets for Cloud DB for MongoDB backup export. Identify available destinations to store backup files.

Instructions

List Object Storage buckets available for Cloud DB for MongoDB 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_mongodb_buckets"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (KR, KRS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/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 does not contradict that. The description adds the specific scope (buckets for MongoDB backup export) but does not disclose additional behavioral traits such as pagination, authentication, or the exact structure of results. Since annotations cover the safety profile, the description adds modest value.

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 clear sentence with no redundant words. The purpose is front-loaded with the verb 'List' and the resource is specified immediately. Highly concise and well-structured.

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 list tool with one optional parameter and no output schema, the description is sufficient to convey purpose and scope. It lacks any mention of return format, but that is not critical given the tool name and nature. The description is complete enough for an agent to select and call it.

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% (regionCode has a description), so the schema fully documents the parameter. The description adds no additional parameter semantics, so the baseline 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 exact resource ('Object Storage buckets available for Cloud DB for MongoDB backup export'). It clearly distinguishes from sibling tools like ncloud_list_mongodb_backups (which lists backups) and ncloud_list_buckets (which lists all buckets).

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 usage context (for MongoDB backup export) but does not explicitly state when to use this tool versus alternatives, nor provide exclusions. It gives some contextual guidance but lacks direct 'use when' or 'alternatives' statements.

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