ncloud-gov-mcp-server

ncloud_change_postgresql_users

Idempotent

Update passwords for PostgreSQL users in a Cloud DB for PostgreSQL instance. Provide the instance number and a list of users with new passwords.

Instructions

Change user information (password) for 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_change_postgresql_users"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description simply restates the operation without adding behavioral context beyond the annotations. Annotations already declare idempotentHint and destructiveHint, but the description adds no practical details such as whether changing a password affects active connections, requires admin rights, or fails for nonexistent users.

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, front-loaded sentence with no wasted words. It efficiently communicates the core purpose without padding.

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 two-parameter tool with annotations and a complete schema, the description is minimally viable but leaves gaps. It doesn't mention that this tool only modifies existing users or that the instance number can be obtained via listing tools, so an agent may not have full operational context.

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%, with both cloudPostgresqlInstanceNo and cloudPostgresqlUserList clearly described. The description's phrase 'user information (password)' aligns with the password field but adds negligible extra meaning, matching the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action ('Change') and the resource ('user information (password) for a Cloud DB for PostgreSQL instance'), distinguishing it from sibling tools like ncloud_add_postgresql_users or ncloud_delete_postgresql_users. However, it doesn't explicitly state that it modifies existing users only, leaving slight ambiguity about scope.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention that adding new users should use ncloud_add_postgresql_users or that listing existing users is available via ncloud_list_postgresql_users, so the agent gets no decision support.

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

Deploy Server