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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_add_acg_inbound_rule

Add an inbound rule to a Naver Cloud Access Control Group to permit traffic by protocol, port range, and source IP or ACG.

Instructions

Add an inbound rule to an 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": {
      "vpcNo": "<vpcNo>",
      "accessControlGroupNo": "<accessControlGroupNo>",
      "protocolTypeCode": "<protocolTypeCode>"
    },
    "name": "ncloud_add_acg_inbound_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
vpcNoYesVPC number (required)
ipBlockNoAccess source IP block in CIDR format (e.g., 0.0.0.0/0). Cannot be used with accessControlGroupSequence.
portRangeNoAllowed port range (e.g., 22, 1-65535). Required if protocol is TCP or UDP.
protocolTypeCodeYesProtocol type code (TCP, UDP, ICMP, or 1-254 protocol number)
accessControlGroupNoYesACG number to add rule to (required)
accessControlGroupSequenceNoAccess source ACG number (alternative to ipBlock). Cannot be used with ipBlock.
accessControlGroupRuleDescriptionNoRule description (0-1000 bytes)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.3/5.0
Behavior2/5

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

The description adds no behavioral context beyond what the destructiveHint=false annotation already conveys. It does not state whether the rule is immediately applied, whether duplicate rules are prevented, or what the API response contains. For a mutation tool, this is a minimal level of transparency.

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 immediately communicates the action and target, making it easy to scan.

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?

Given the rich input schema, the description is minimally viable but lacks operational context. It does not mention return values (no output schema) or the distinction from outbound rule addition, which would help an agent fully understand the tool's role. The moderate complexity (7 params, conditional rules) is partially addressed by the schema, but the description alone would be insufficient for a new user.

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 provides 100% coverage with descriptions for all seven parameters, including conditional requirements (e.g., portRange required for TCP/UDP) and mutual exclusivity (ipBlock vs accessControlGroupSequence). The tool description itself does not add any parameter semantics, so the baseline score of 3 applies.

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 verb 'Add' and the resource 'inbound rule to an Access Control Group'. The word 'inbound' differentiates it from the sibling tool ncloud_add_acg_outbound_rule, making the tool's specific role unmistakable.

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?

The description provides no guidance on when to use this tool versus alternatives, such as ncloud_add_acg_outbound_rule. It also does not mention any prerequisites (e.g., needing an existing ACG or VPC). The only implied usage is from the tool name itself, which is insufficient for an agent to choose confidently.

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