ncloud-gov-mcp-server

ncloud_add_postgresql_users

Add new users to a Cloud DB for PostgreSQL instance by specifying the instance number and a list of usernames and passwords.

Instructions

Add users to a Cloud DB for PostgreSQL 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": {
      "cloudPostgresqlInstanceNo": "<cloudPostgresqlInstanceNo>",
      "cloudPostgresqlUserList": "<cloudPostgresqlUserList>"
    },
    "name": "ncloud_add_postgresql_users"
  }
}

Input Schema

Name	Required	Description	Default
`cloudPostgresqlUserList`	Yes	List of users to add
`cloudPostgresqlInstanceNo`	Yes	Cloud PostgreSQL instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With only destructiveHint=false provided, the description adds no behavioral context beyond the annotation. It does not disclose what happens if a user already exists, whether the operation is idempotent, or any prerequisites. The description merely restates the action without revealing operational implications.

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 that is front-loaded with the action and resource. It is concise, free of unnecessary words, and easy to parse.

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 description is adequate for a simple add operation with full schema coverage, but it lacks usage guidelines and behavioral context. Given the presence of many sibling tools with similar names, the description alone may not fully prepare an agent to choose and invoke this tool correctly.

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?

The input schema already provides descriptions for both parameters with 100% coverage. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 action ('Add users') and the specific resource ('Cloud DB for PostgreSQL instance'), which distinguishes it from sibling tools for other database engines (e.g., MySQL, MongoDB) and from related PostgreSQL operations like change/delete/list users.

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. It does not mention that this creates new database users, nor does it point to change_postgresql_users for modifying existing users or delete_postgresql_users for removing them. There is no context about prerequisites or when this operation 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