Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_create_mongodb_instance

Create a Cloud DB for MongoDB instance. Enable dry run to preview the configuration before committing.

Instructions

Create a new Cloud DB for MongoDB 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
subnetNoYesSubnet number
configPortNoConfig port (default 17017)
memberPortNoMember port (default 17017, range 10000-65535)
mongosPortNoMongos port (default 17017)
shardCountNoNumber of shards (2-3, for SHARDED_CLUSTER)
compressCodeNoCompression algorithm (SNPP | ZLIB | ZSTD | NONE)
clusterTypeCodeYesCluster type code (STAND_ALONE | SINGLE_REPLICA_SET | SHARDED_CLUSTER)
configProductCodeNoConfig server product code
configServerCountNoNumber of config servers (for sharded cluster)
engineVersionCodeNoMongoDB engine version code
memberProductCodeNoMember server product code
memberServerCountNoNumber of member servers in the replica set
mongosProductCodeNoMongos server product code
mongosServerCountNoNumber of mongos servers (for sharded cluster)
arbiterProductCodeNoArbiter server product code
arbiterServerCountNoNumber of arbiter servers
dataStorageTypeCodeNoData storage type (SSD | HDD | CB2)
cloudMongoDbUserNameYesInitial admin user name
cloudMongoDbServiceNameYesMongoDB service name (3-20 chars, lowercase letters and numbers)
cloudMongoDbUserPasswordYesInitial admin user password
backupFileRetentionPeriodNoBackup retention period in days (1-30)
cloudMongoDbImageProductCodeNoMongoDB image product code
cloudMongoDbServerNamePrefixYesServer name prefix
Behavior3/5

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

Annotations already indicate destructiveHint=false. The description adds the dryRun option but does not disclose other behaviors like required permissions, creation duration, or success/failure conditions.

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 extremely concise with two sentences, no extraneous information, and front-loads the core purpose.

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 complexity (25 parameters, no output schema), the description is minimal. It covers the basic action and a key option but omits details about return values or prerequisites, leaving gaps for the agent.

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 all parameters are already documented. The tool description adds no additional semantic value beyond the schema.

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 clearly states the verb 'Create' and the specific resource 'Cloud DB for MongoDB instance', which distinguishes it from sibling tools for other databases like MySQL or PostgreSQL.

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 a specific usage tip: 'Use dryRun=true to preview without creating.' This offers clear guidance for safe invocation, though it does not explicitly contrast with alternatives.

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