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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_deny_allow_group_detail

Read-only

Get detailed information about a Deny-Allow Group by group number to review its rules and network ACL configuration.

Instructions

Get detailed information about a specific Deny-Allow 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": {
      "networkAclDenyAllowGroupNo": "<networkAclDenyAllowGroupNo>"
    },
    "name": "ncloud_get_deny_allow_group_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkAclDenyAllowGroupNoYesDeny-Allow Group number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint: true, so the read-only nature is known. The description adds only 'Get detailed information', which reiterates the action without enriching behavioral context like response structure, error handling, or required permissions. No contradiction with annotations.

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?

Single sentence, front-loaded verb, zero filler. Perfectly concise for a simple get-by-id operation.

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 one-parameter read-only tool with no output schema, the description is adequate. It tells the user the action and resource. Some additional context about return contents could be useful, but given simplicity and annotation, completeness is acceptable.

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 coverage is 100% with parameter 'networkAclDenyAllowGroupNo' described as 'Deny-Allow Group number to query'. The description itself adds no extra meaning beyond the schema, which already documents the purpose of the single parameter.

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?

Description uses specific verb 'Get' with resource 'specific Deny-Allow Group', clearly distinguishing it from sibling tools like list_deny_allow_groups. The 'specific' qualifier signals this fetches one entity by identifier, differentiating it from list operations.

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?

The description implies usage when you need details for an individual Deny-Allow Group, but provides no explicit when/or not to use alternatives such as the list tool. No exclusions or alternative guidance is given, so the context is only implied.

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