ncloud-gov-mcp-server

ncloud_create_monitor_group

Create a monitoring target group in Cloud Insight by specifying a product key, group name, and resource dimensions to organize resources for unified monitoring and alerts.

Instructions

Create a new Cloud Insight monitoring target 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": {
      "prodKey": "<prodKey>",
      "groupName": "<groupName>",
      "resourceList": "<resourceList>"
    },
    "name": "ncloud_create_monitor_group"
  }
}

Input Schema

Name	Required	Description
`prodKey`	Yes	Product key (cw_key) for the target service
`groupName`	Yes	Name of the monitor group
`resourceList`	Yes	Array of resource dimension objects to include in the group

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?

Aside from the single annotation indicating destructiveHint=false, the description adds no behavioral details such as idempotency, permissions, return values, or side effects. 'Create a new' minimally implies a mutation but doesn't disclose anything beyond what the annotation already partially covers.

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 concise sentence, immediately front-loaded with the action verb and resource. No filler words; the Korean translation in parentheses is a harmless addition.

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?

Given the tool is a create operation within the Cloud Insight monitoring domain, the description doesn't explain what a target group is, how it relates to metrics groups or rules, or what the API returns. With no output schema and only minimal annotation, the agent lacks context to use this tool confidently.

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 descriptions cover all three parameters (100% coverage), so the baseline is 3. The tool description itself doesn't add parameter context, but the schema already explains prodKey, groupName, and resourceList sufficiently.

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 'Create' with the resource 'Cloud Insight monitoring target group,' clearly distinguishing it from sibling operations like list, get, update, and delete monitor group. The Korean parenthetical provides a localized alias but doesn't introduce ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention related operations or prerequisites, so an agent must infer usage solely from the name and verb.

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

Deploy Server