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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_rule_groups

Read-only

List Cloud Insight event rule groups to monitor alerts. Filter by product key and search keyword, with pagination support.

Instructions

Get the list of Cloud Insight event rule groups for monitoring alerts.

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>",
      "pageSize": "<pageSize>",
      "pageNum": "<pageNum>"
    },
    "name": "ncloud_list_rule_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoSearch keyword to filter rule groups
pageNumYesPage number (required, starts from 1)
prodKeyYesProduct key (cw_key) to filter rule groups (required)
pageSizeYesNumber of results per page (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior3/5

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

The description aligns with the readOnlyHint annotation (says 'Get'), but adds no behavioral details beyond that. It provides domain context by mentioning 'Cloud Insight' and 'monitoring alerts,' but does not disclose pagination behavior or filtering constraints already present in 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence with no filler. It is front-loaded with the main verb and resource, making it easy to scan. While concise, it omits any supplementary usage or context details, but remains economical.

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?

For a simple list operation with pagination parameters and a read-only annotation, the description is adequate but minimal. It doesn't explain what a 'rule group' is or that results are paginated, relying on the schema for parameter details. Given the lack of an output schema, the description could clarify return format, but the core purpose is clear.

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 has 100% description coverage for all four parameters, so the description does not need to repeat parameter semantics. The schema already describes prodKey as 'cw_key' filter, pageSize/Num, and search keyword. The description adds no additional meaning beyond the schema, so it meets the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Get') and resource ('list of Cloud Insight event rule groups'), clearly indicating a listing operation. It distinguishes from sibling tools like get_rule_group (single) and create/delete/update variants by focusing on list retrieval. However, it could more explicitly mention that this returns all rule groups (with pagination) to fully disambiguate.

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 get_rule_group for a single rule group or list_metrics_groups for other monitoring resources. The description only states what the tool does, leaving the agent to infer usage from the tool name.

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