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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_rules_by_monitor_group

Read-only

Retrieves Cloud Insight event rules for the given monitoring target group IDs, clarifying which rules apply to each group.

Instructions

Get Cloud Insight event rules associated with specific monitoring target group IDs.

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": {
      "monitorGroupIds": "<monitorGroupIds>"
    },
    "name": "ncloud_get_rules_by_monitor_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitorGroupIdsYesArray of monitor group IDs to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, and the description's 'Get' matches that safe read behavior. The description adds no further behavioral context beyond the read-only hint, such as pagination or response format, but with annotations present this is acceptable.

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 that directly states the action and resource. No unnecessary words or repetition.

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?

Given the simplicity of the tool (one parameter, read-only, no output schema), the description sufficiently conveys purpose and scope. It does not mention return format, but the operation is straightforward and the name further clarifies intent.

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 covers 100% of parameters with a clear description of 'monitorGroupIds'. The tool description's phrasing 'monitoring target group IDs' is essentially synonymous and does not add meaningful new meaning beyond the schema.

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 a specific verb ('Get') and resource ('Cloud Insight event rules'), and clarifies association with 'specific monitoring target group IDs'. This clearly distinguishes it from sibling tools like ncloud_get_rules_by_metrics_group and ncloud_remove_resource_from_rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use this tool: when you need event rules for specific monitoring target group IDs. However, it does not explicitly mention alternatives or when-not-to-use conditions, which would merit a 5.

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