ncloud-gov-mcp-server

ncloud_create_rule_group

Creates a Cloud Insight event rule group to define monitoring targets, metrics, thresholds, and alert notifications.

Instructions

Create a new Cloud Insight event rule group for monitoring alerts. Defines monitoring targets, metrics, thresholds, and notification recipients.

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": {
      "groupName": "<groupName>",
      "prodKey": "<prodKey>",
      "metricsGroupId": "<metricsGroupId>",
      "monitorGroupId": "<monitorGroupId>",
      "cfgRuleList": "<cfgRuleList>"
    },
    "name": "ncloud_create_rule_group"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, returns a preview without creating the rule group (default: false)
`prodKey`	Yes	Product key (cw_key) for the target service
`groupName`	Yes	Name of the rule group
`cfgRuleList`	Yes	List of rule configurations defining alert conditions
`metricsGroupId`	Yes	Metrics group ID (rule template) to apply
`monitorGroupId`	Yes	Monitor group ID (target group) to monitor
`recipientNotification`	No	Notification recipients for alerts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations only state destructiveHint=false, which is expected for a create operation. The description adds no behavioral context beyond 'Create a new', such as whether the rule group becomes active immediately, permission requirements, or side effects. It does not disclose that dryRun can preview without creating, which is a valuable behavioral trait not obvious from the schema.

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 two sentences with no redundant phrasing. The first sentence states the core action and resource, the second summarizes key components. Every phrase earns its place.

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

Completeness2/5

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

This is a complex creation tool with 7 parameters, nested arrays, and no output schema. The description does not reference prerequisites (e.g., needing existing metrics groups or monitor groups) or related list tools, nor does it mention validation behavior or the existence of dryRun for preview. For its complexity, the 2-sentence description is incomplete.

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%, so parameter descriptions exist in structured form. The tool description adds a high-level summary ('Defines monitoring targets, metrics, thresholds, and notification recipients') that groups parameters conceptually, but it does not explain relationships between parameters or provide value beyond what the schema already conveys. 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 verb 'Create' and the resource 'Cloud Insight event rule group', distinguishing it from update/list/delete siblings. It further defines the scope by mentioning monitoring targets, metrics, thresholds, and notifications, which is specific and unambiguous.

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 explicit guidance on when to use this tool versus alternatives like ncloud_create_rule_directly, nor does it mention prerequisites such as needing existing metricsGroupId and monitorGroupId. There is no exclusionary language or reference to related list/read tools for setup.

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

Deploy Server