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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_acg_detail

Read-only

Retrieve detailed configuration for a specific Access Control Group using its unique number to inspect rules and settings in Naver Cloud Platform.

Instructions

Get detailed information about a specific Access Control Group

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": {
      "accessControlGroupNo": "<accessControlGroupNo>"
    },
    "name": "ncloud_get_acg_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessControlGroupNoYesAccess Control Group number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so the safety profile is already conveyed. The description adds that it returns 'detailed information' about a specific ACG but does not disclose response format, pagination, error behavior, or permission requirements. With annotations covering the key behavioral concern, a score of 3 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, front-loaded sentence that clearly states the action and resource with no filler or redundancy. It is immediately scannable and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only tool with one well-documented parameter, the description is sufficient to convey the tool's purpose and scope. No output schema is required for understanding the basic operation, and the sibling tool context clarifies naming conventions.

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 has 100% coverage for the single required parameter (accessControlGroupNo), which already includes a description. The tool description adds no extra parameter-level semantics beyond the existing schema and the word 'specific', which is implicit in the endpoint.

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 a specific verb ('Get') with a clear resource ('Access Control Group') and scope ('detailed information about a specific'). This distinguishes it from sibling tools like ncloud_list_acgs (which lists all) and ncloud_get_acg_rules (which fetches rules).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is provided on when to use this tool versus alternatives such as ncloud_list_acgs or ncloud_get_acg_rules. The word 'specific' implies it is for a single ACG, but the description does not mention alternatives or exclusions.

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