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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_change_mongodb_users

Idempotent

Change passwords for users of a Cloud DB for MongoDB instance by providing the instance number and a list of users with new passwords.

Instructions

Change user information (password) in a Cloud DB for MongoDB 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>",
      "cloudMongoDbUserList": "<cloudMongoDbUserList>"
    },
    "name": "ncloud_change_mongodb_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudMongoDbUserListYesList of users to change
cloudMongoDbInstanceNoYesCloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the tool as idempotent and non-destructive. The description adds that it changes password within a MongoDB DB instance, but does not disclose behavioral details such as whether users must already exist, password format constraints, or impact on active connections. It provides minimal additional context beyond the annotations.

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 sentence, front-loaded with the verb and target, with no unnecessary words or repetition of schema fields. It gets straight to the point.

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?

The tool is simple and parameters are fully described, but the description lacks important context for a mutation: no mention that it applies to existing users, no password constraints, and no indication of return value or async behavior (no output schema). It is adequate for basic invocation but leaves some practical questions unanswered.

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 coverage is 100%: both parameters have clear descriptions (instance number, list of users with name and new password). The description restates 'password' but adds no extra semantic detail beyond what the schema already provides, so the baseline of 3 applies.

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 operation (change), target resource (user information/password), and scope (Cloud DB for MongoDB instance). The verb 'change' distinguishes it from sibling tools like ncloud_add_mongodb_users and ncloud_delete_mongodb_users, making the tool's purpose unambiguous.

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 explicit guidance on when to use this tool versus alternatives. It does not mention that it updates existing users, distinguish it from add/delete operations, or note any prerequisites. The agent must infer usage from tool naming alone.

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