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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_hadoop_save_hive_metastore

Configure Cloud Hadoop cluster to use an external Hive metastore by providing MySQL instance, database, and credentials.

Instructions

Save external Hive metastore configuration to Cloud Hadoop cluster

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cloudHadoopInstanceNo": "<cloudHadoopInstanceNo>",
      "cloudMysqlInstanceNo": "<cloudMysqlInstanceNo>",
      "cloudMysqlUserName": "<cloudMysqlUserName>",
      "cloudMysqlUserPassword": "<cloudMysqlUserPassword>",
      "cloudMysqlDatabaseName": "<cloudMysqlDatabaseName>"
    },
    "name": "ncloud_hadoop_save_hive_metastore"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code
cloudMysqlUserNameYesMySQL user name for metastore
cloudMysqlInstanceNoYesCloud DB for MySQL instance number
cloudHadoopInstanceNoYesCloud Hadoop instance number
cloudMysqlDatabaseNameYesMySQL database name for metastore
cloudMysqlUserPasswordYesMySQL user password

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits on its own. It only states the action without revealing side effects (e.g., whether it overwrites existing configuration), validation behavior, or prerequisites. This is insufficient for a mutation operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It is appropriately front-loaded and easy to parse, though it could potentially add more useful context without losing conciseness.

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?

Despite having 6 parameters and no output schema, the description is minimal. It lacks context about what 'save' entails (e.g., updating existing config, verification steps, relationship to the 'test_hive_metastore' tool), making it incomplete for an agent to know when and how to use it safely.

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%, so the schema already documents all parameters. The description itself adds no additional parameter semantics beyond implying they relate to the Hive metastore configuration. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Save external Hive metastore configuration to Cloud Hadoop cluster' uses a specific verb ('save') and identifies the resource ('external Hive metastore configuration') and destination ('Cloud Hadoop cluster'). It clearly states the operation, though it does not explicitly distinguish itself from the sibling tool 'ncloud_hadoop_test_hive_metastore', which seems related.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or contrast with sibling tools like 'test_hive_metastore' or 'backup_config'.

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