ncloud-gov-mcp-server

ncloud_create_metrics_group

Create a Cloud Insight metrics group to monitor service metrics. Specify product key, group name, and metric rules with thresholds, conditions, durations, and event levels to define alert conditions.

Instructions

Create a new Cloud Insight rule template (감시 항목 그룹 / metrics 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>",
      "metricList": "<metricList>"
    },
    "name": "ncloud_create_metrics_group"
  }
}

Input Schema

Name	Required	Description
`prodKey`	Yes	Product key (cw_key) for the target service
`groupName`	Yes	Name of the metrics group
`metricList`	Yes	List of metric configurations

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description aligns with the non-destructive annotation (destructiveHint: false) since 'Create' implies a benign write operation. However, it adds no additional behavioral context such as idempotency, permissions, validation rules, or what happens on duplicates. With annotations present, the absence of contradiction warrants a baseline 3, but no extra credit is earned.

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 filler. It packs the core purpose and the Korean synonym into minimal words, making it easy to scan and remember.

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?

With 3 well-documented parameters and no output schema, the description could be more helpful by explaining the relationship between metrics groups and rule groups, or what the response includes (e.g., group ID). It is adequate for a simple create but omits surrounding context that sibling tools and the Cloud Insight ecosystem imply.

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 description coverage is 100%, with prodKey, groupName, and metricList all documented in the input schema. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies as the schema already carries semantic weight.

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 'Create a new Cloud Insight rule template (감시 항목 그룹 / metrics group)' specifies a clear verb and resource, and explicitly names the Korean term to disambiguate from sibling tools like create_rule_group and create_monitor_group. It distinguishes the metrics group entity while staying concise.

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 such as ncloud_create_rule_group, ncloud_create_monitor_group, or ncloud_update_metrics_group. The description does not mention prerequisites, typical scenarios, or any exclusion criteria, leaving the agent to infer usage purely from the name.

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

Deploy Server