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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_change_mongodb_shard_count

Idempotent

Change the shard count of a MongoDB Sharded Cluster instance to adjust data distribution and capacity as workload demands evolve.

Instructions

Change the number of shards in a MongoDB Sharded Cluster instance

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": {
      "cloudMongoDbInstanceNo": "<cloudMongoDbInstanceNo>",
      "shardCount": "<shardCount>"
    },
    "name": "ncloud_change_mongodb_shard_count"
  }
}

Input Schema

NameRequiredDescriptionDefault
shardCountYesNumber of shards
cloudMongoDbInstanceNoYesCloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds minimal behavioral context beyond specifying the target resource (Sharded Cluster), but discloses no operational details such as whether the change is asynchronous, requires downtime, or has side effects.

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 that immediately states the action and target, with no filler or redundancy.

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 low-complexity operation with fully documented parameters and safety annotations, the description is largely sufficient. It clearly states the resource type, but omits any mention of result behavior or preconditions, which would push it to a 5.

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% (both parameters have descriptions), so the schema already explains the parameters. The tool description does not add any additional meaning or format details for the parameters, keeping it at the baseline.

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 uses a specific verb 'Change' and clearly identifies the resource ('number of shards in a MongoDB Sharded Cluster instance'), which distinguishes it from sibling tools that change other MongoDB counts (e.g., ncloud_change_mongodb_secondary_count, ncloud_change_mongodb_mongos_count).

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, nor does it mention prerequisites or conditions. It only states what the tool does, leaving usage context unstated.

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