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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_notebook_images

Read-only

List available Hadoop notebook image products by region code to identify which images you can use for notebook instances.

Instructions

List available notebook image products

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

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.1/5.0
Behavior2/5

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

The readOnlyHint annotation already indicates this is a safe read operation, so the description does not need to repeat that. However, it adds no additional behavioral context such as pagination, region-scoping behavior, or relationship between 'image products' and other listing tools. The description barely goes beyond the name and annotation.

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 phrase that conveys the essential purpose without filler. Every word adds value, and it is appropriately sized for a simple list operation.

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

Completeness3/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description is minimally adequate but leaves gaps. It does not clarify what an 'image product' is, whether regionCode is needed to scope results, or what the response format looks like. The absence of an output schema makes some return-value context desirable.

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% since the only parameter, regionCode, is described as 'Region code'. The description itself provides no parameter-specific details beyond what the schema already states, so the baseline of 3 applies.

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 'List available notebook image products' clearly states the action (list) and the resource (notebook image products). It is specific enough to distinguish from generic list tools, though it does not explicitly differentiate from the closely related sibling tool ncloud_hadoop_list_notebook_products.

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?

No guidance is provided on when to use this tool versus alternatives such as ncloud_hadoop_list_notebook_products or ncloud_hadoop_list_image_products. The description does not mention any exclusions, preconditions, or use cases, leaving the agent without comparative 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