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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_list_login_keys

Read-only

List SSH login keys available for Cloud Hadoop access. Retrieve the keys needed to configure SSH connections to your cluster.

Instructions

List login keys available for Cloud Hadoop SSH access

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

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, which the description aligns with via 'List'. The description adds the Hadoop SSH access scope but does not disclose further behavioral traits such as pagination, filtering behavior, or response format. Given the annotations cover the safety profile, this is adequate but not rich.

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 of 10 words, front-loaded with the action verb 'List' followed by the specific resource and scope. There is zero wasted text.

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 read-only list operation with one optional parameter, the description covers the essential purpose and scope, making it sufficient for tool selection and invocation. It could be slightly richer with explicit alternative guidance, but the current level of detail is adequate given the tool's simplicity.

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?

Input schema coverage is 100%, with regionCode described as 'Region code' in the schema. The description does not mention parameters, but since the schema fully documents the only parameter, the baseline of 3 applies. No additional parameter semantics are needed.

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?

Description uses specific verb 'List' with resource 'login keys' scoped to 'Cloud Hadoop SSH access', clearly identifying its function. It distinguishes itself from the general ncloud_list_login_keys and the SES-specific ncloud_ses_get_login_keys siblings by the Hadoop context.

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 description provides clear context about when to use this tool (for Cloud Hadoop SSH login keys), which effectively guides selection among siblings that operate on different resource types. It does not explicitly name alternatives or exclusions, but the Hadoop scope makes the intended use unambiguous.

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