Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_create_cache_instance

Create a new Redis or Valkey cache instance with options for backup, clustering, and failover. Use dryRun to preview before actual creation.

Instructions

Create a new Cloud DB for Cache (Redis/Valkey) instance. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpcNoYesVPC number
dryRunNoIf true, returns a preview without actually creating the instance
isBackupNoWhether to enable automatic backup
subnetNoYesSubnet number
backupTimeNoBackup time (HH:mm format)
shardCountNoNumber of shards (for cluster mode)
cloudCachePortNoCache port number (default: 6379)
shardCopyCountNoNumber of replicas per shard
isAutomaticFailoverNoWhether to enable automatic failover
cloudCacheProductCodeNoCache server product (spec) code
cloudCacheServiceNameYesCache service name (3-20 chars, lowercase letters and numbers)
cloudCacheConfigGroupNoNoConfig group number to apply
backupFileRetentionPeriodNoBackup retention period in days (1-30)
cloudCacheImageProductCodeNoCache image product code (Redis/Valkey version)
cloudCacheServerNamePrefixNoServer name prefix
Behavior2/5

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

Annotations already indicate non-destructive behavior. The description adds the dryRun preview feature but fails to disclose other behavioral traits like required permissions, failure handling, or output format.

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?

Two sentences, front-loaded with the primary purpose, and no extraneous information.

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?

Given 15 parameters and the complexity of creating a cache instance, the description is too minimal. It lacks prerequisites (e.g., VPC/subnet existence) and output details, even though schema coverage is good.

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?

All 15 parameters have schema descriptions (100% coverage), so the description does not need to add detail. It mentions dryRun but that is already in the schema.

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 tool creates a Cloud DB for Cache (Redis/Valkey) instance, with a specific verb and resource. However, it does not differentiate from sibling cache tools like ncloud_create_cache_config_group.

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?

Provides a usage tip for dryRun but offers no guidance on when to use this tool versus alternatives such as listing instances or backup creation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server