ncloud-gov-mcp-server

ncloud_hadoop_list_buckets

Read-only

List Object Storage buckets associated with a Cloud Hadoop instance using region code and instance number.

Instructions

List Object Storage buckets available for Cloud Hadoop

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_hadoop_list_buckets"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code
`cloudHadoopInstanceNo`	No	Cloud Hadoop 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?

With readOnlyHint=true, the agent knows this is a safe read operation. The description adds the 'available for Cloud Hadoop' scope, but does not disclose whether it returns only buckets linked to a specific instance, what happens if cloudHadoopInstanceNo is omitted, or any details about the returned data. This goes little beyond what the annotation already conveys.

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 concise sentence with no wasted words. It is front-loaded with the verb and resource, making it easy to scan and parse.

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?

The tool has no output schema, so the description should compensate by explaining what is returned, but it does not. It also does not address optional parameters or behavior when no Cloud Hadoop instance is specified. While simple, it leaves important gaps for an agent to invoke the tool 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% (both parameters have descriptions: 'Region code' and 'Cloud Hadoop instance number'), so the schema carries the load. The description does not add any parameter-specific meaning beyond that, so a baseline score of 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'), the resource ('Object Storage buckets'), and the context ('for Cloud Hadoop'). This differentiates it from generic bucket-listing tools like ncloud_list_buckets, though the scope 'available for Cloud Hadoop' is somewhat broad and could be more specific.

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 does not say when to use this tool versus alternatives such as ncloud_list_buckets or ncloud_ses_get_snapshot_buckets. There is no mention of prerequisites, filtering scenarios, or when to prefer this tool over siblings. The only usage signal is the name and brief 'for Cloud Hadoop' context.

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

Deploy Server