ncloud-gov-mcp-server

ncloud_add_mongodb_users

Add users to a Cloud DB for MongoDB instance, specifying user credentials, database, and access authority.

Instructions

Add users to 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_add_mongodb_users"
  }
}

Input Schema

Name	Required	Description	Default
`cloudMongoDbUserList`	Yes	List of users to add
`cloudMongoDbInstanceNo`	Yes	Cloud MongoDB instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior2/5

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

The only annotation is destructiveHint: false, which conflicts with nothing. The description adds no behavioral details beyond what the name suggests, such as idempotency, error scenarios, or prerequisites. With annotations covering the safety profile, the description still offers no extra context, so a score of 2 reflects the lack of added transparency.

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 with no redundant information, front-loading the action and target. It earns a 5 for efficiency and clarity.

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?

For a simple add operation, the description is functional but minimal. It does not mention response behavior, side effects, or validation rules, and there is no output schema to compensate. While the schema covers parameters, the description alone provides limited context beyond the tool's purpose, so a 3 is reasonable.

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% with clear descriptions for both parameters and nested user fields. The description does not add any additional meaning or clarify parameter usage, 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 uses the specific verb 'Add' with the resource 'users' and target 'Cloud DB for MongoDB instance', clearly distinguishing it from sibling tools like ncloud_list_mongodb_users, ncloud_change_mongodb_users, and ncloud_delete_mongodb_users.

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 context is clear: this tool is for adding users to a MongoDB instance. However, it lacks explicit guidance about when not to use it (e.g., for modifying existing users) or mentions of alternatives. The verb 'Add' alone implies creation, but no explicit exclusions are stated, so a 4 is appropriate.

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

Deploy Server