ncloud-gov-mcp-server

ncloud_set_deny_allow_group_desc

Idempotent

Set or update the description of a Network ACL Deny-Allow Group. Provide the group number and new description to manage its metadata.

Instructions

Set or update the description of a Network ACL 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>",
      "networkAclDenyAllowGroupDescription": "<networkAclDenyAllowGroupDescription>"
    },
    "name": "ncloud_set_deny_allow_group_desc"
  }
}

Input Schema

Name	Required	Description	Default
`networkAclDenyAllowGroupNo`	Yes	Deny-Allow Group number
`networkAclDenyAllowGroupDescription`	Yes	New description for the Deny-Allow Group

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/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. The description adds the 'Set or update' semantics which aligns with idempotency, but does not disclose additional behavioral details such as whether the description is overwritten or if the group must exist.

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 sentence with no unnecessary words, front-loading the action and resource.

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 simple two-parameter update operation with annotations covering idempotency and non-destructiveness, the description is largely sufficient. However, it does not mention any effects on existing data or error conditions, leaving some nuance implicit.

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?

Both parameters are fully documented in the input schema with descriptions ('Deny-Allow Group number' and 'New description for the Deny-Allow Group'). The tool description adds no further parameter-level meaning beyond the schema's 100% coverage.

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 the specific verb 'Set or update' and names the exact resource 'description of a Network ACL Deny-Allow Group', clearly distinguishing it from sibling tools like ncloud_set_network_acl_description and ncloud_create_deny_allow_group.

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 provides a clear statement of the tool's action but does not explicitly state when to use this tool versus alternatives, nor any exclusions or prerequisites. Context must be inferred from the resource name.

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

Deploy Server