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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_change_cache_users

Idempotent

Change DB user passwords for a Cloud DB for Cache (Redis/Valkey) instance. Provide the instance number and a list of users with new credentials.

Instructions

Change DB user passwords for a Cloud DB for Cache (Redis/Valkey) 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": {
      "cloudCacheInstanceNo": "<cloudCacheInstanceNo>",
      "cloudCacheUserList": "<cloudCacheUserList>"
    },
    "name": "ncloud_change_cache_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (KR, KRS)
cloudCacheUserListYesList of users to modify
cloudCacheInstanceNoYesCloud Cache instance number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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, covering the safety profile. The description adds no further behavioral context, such as side effects on existing connections or partial failure behavior when changing multiple passwords. It does not contradict the annotations, so a baseline score is appropriate.

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, direct sentence with no unnecessary words. It states the action and resource efficiently, making it easy for an agent to parse.

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 mutating tool with comprehensive schema coverage and clear annotations, the description provides enough context to select and invoke the tool correctly. It does not explain return values or sync/async behavior, but the schema and annotations compensate, leaving only minor gaps.

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 parameters like cloudCacheUserList and cloudCacheInstanceNo fully described. The description adds no extra semantic detail beyond confirming that passwords are being changed, which aligns with the schema. Baseline 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 ('Change'), the resource ('DB user passwords'), and the target ('Cloud DB for Cache (Redis/Valkey) instance'). This distinguishes it from sibling tools like add_cache_users, delete_cache_users, and list_cache_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?

No guidance is provided on when to use this tool versus alternatives such as adding or deleting cache users. The description explains the operation but does not mention scenarios (e.g., password rotation) or exclusions (e.g., cannot create new users). This leaves the agent without context for tool selection.

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