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_metrics_group

Read-only

Retrieve Cloud Insight event rules by providing metrics group IDs to monitor specific rule templates.

Instructions

Get Cloud Insight event rules associated with specific rule template (metrics 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": {
      "metricsGroupIds": "<metricsGroupIds>"
    },
    "name": "ncloud_get_rules_by_metrics_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricsGroupIdsYesArray of metrics group IDs to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description need not repeat safety. It adds the context that these are event rules tied to rule template (metrics group) IDs, but doesn't disclose any further behavioral details like pagination or response structure.

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?

One sentence of 14 words, front-loaded with the action and object. No wasted words.

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?

For a simple read operation with one documented parameter and a readOnly annotation, the description plus schema cover the essentials. It doesn't describe the return format, but with no output schema and a 'Get' verb, that's not a critical gap for a competent agent.

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 single parameter metricsGroupIds is fully documented in the schema (100% coverage), so the description doesn't need to explain it further. The tool description repeats the parameter concept but adds no additional semantics about how to obtain or format the IDs.

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 names the resource ('Cloud Insight event rules') with a clear filter ('by metrics group IDs'). It distinguishes from the sibling 'ncloud_get_rules_by_monitor_group' by specifying the grouping dimension.

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

Usage Guidelines3/5

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

Usage context is implied: use this tool when you need rules filtered by metrics group IDs. However, it doesn't explicitly state when not to use this tool or mention the alternative 'ncloud_get_rules_by_monitor_group' for monitor group-based queries.

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