ncloud-gov-mcp-server

ncloud_list_cache_users

Read-only

List database users (ACL) for a Cloud DB for Cache (Redis/Valkey) instance to review or manage access control.

Instructions

List DB users (ACL) of 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>"
    },
    "name": "ncloud_list_cache_users"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code (KR, KRS)
`cloudCacheInstanceNo`	Yes	Cloud Cache instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

The readOnlyHint annotation already marks this as a safe read operation, and the description's 'List' verb is consistent. The description adds no extra behavioral detail such as pagination, response format, or access prerequisites, so it provides only basic transparency beyond the annotation.

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, complete sentence that directly states the tool's purpose. No superfluous words, and the key scoping qualifiers (DB users, ACL, Redis/Valkey) are positioned clearly.

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?

The tool has two well-documented parameters and a clear listing purpose; the description sufficiently conveys what the tool does. It lacks any mention of output structure or pagination, but given the simplicity and existing schema documentation, it is complete enough for an agent to invoke the 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?

Schema description coverage is 100%; both regionCode and cloudCacheInstanceNo have descriptive text in the schema. The tool description does not add any parameter semantics beyond what the schema already provides, so 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 ('List'), the resource ('DB users (ACL)'), and the target system ('Cloud DB for Cache (Redis/Valkey) instance'). It distinguishes this from sibling tools like ncloud_add_cache_users, ncloud_change_cache_users, and ncloud_delete_cache_users, which perform mutations.

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 description provides clear context that this is the read-only listing operation for cache DB users. It does not explicitly mention when not to use it or direct to alternatives, but the contrast with mutation siblings is evident from the tool name and context.

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

Deploy Server