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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_notebook_buckets

Read-only

List Object Storage buckets linked to a Cloud Hadoop notebook cluster to verify available data sources for notebook tasks.

Instructions

List Object Storage buckets available for Cloud Hadoop notebooks

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

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code
cloudHadoopInstanceNoNoCloud Hadoop instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.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's 'List' verb aligns with that. The description adds the scope constraint ('available for Cloud Hadoop notebooks'), but provides no additional behavioral details such as pagination, required permissions, or default region 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?

The description is a single, front-loaded sentence that conveys the essential purpose with no wasted words. Every word contributes to understanding the tool's scope.

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?

Given the low complexity, read-only annotation, and fully described schema parameters, the description is sufficient for an agent to understand the tool's core behavior. It does not explain return values, but no output schema exists and this is a simple list operation.

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% for both parameters ('Region code', 'Cloud Hadoop instance number'). The description does not add meaning beyond the schema, 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 resource ('Object Storage buckets') with a clear scope ('available for Cloud Hadoop notebooks'). This distinguishes it from siblings like ncloud_hadoop_list_buckets by limiting to notebook-available 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 phrase 'available for Cloud Hadoop notebooks' implies when to use this tool, but it does not explicitly state alternatives, prerequisites, or when not to use it. There is no mention of how this differs from related bucket-listing 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