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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_rule_group

Read-only

Get detailed information about a Cloud Insight event rule group using its ID. View configuration and settings to manage monitoring alerts.

Instructions

Get detailed information about a specific Cloud Insight event rule 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": {
      "ruleGroupId": "<ruleGroupId>"
    },
    "name": "ncloud_get_rule_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleGroupIdYesRule group ID to retrieve details for

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?

The readOnlyHint annotation already declares the operation as read-only. The description adds domain context ('Cloud Insight event rule group') but no additional behavioral traits such as error behavior, response format, or data included. With annotations present, the bar is lower, and it does not contradict them.

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, well-structured sentence with no redundant information. It is front-loaded with the verb and resource, earning its place fully.

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 low complexity (1 parameter, no output schema, readOnly annotation), the description and schema together provide adequate context for correct invocation. It could specify what 'detailed information' includes, but this is not essential for a simple get-by-id operation.

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%, and the parameter ruleGroupId is already clearly described as 'Rule group ID to retrieve details for'. The tool description adds no additional meaning beyond what the schema provides, so the baseline 3 applies.

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 explicitly identifies the resource as a 'specific Cloud Insight event rule group', clearly distinguishing it from list-type operations. The modifier 'specific' signals a singular retrieval, which differentiates it from ncloud_list_rule_groups.

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?

The description implies usage when a particular rule group ID is known, but it does not explicitly state when not to use it or mention alternatives like ncloud_list_rule_groups. The context is present but only implied, not explicit.

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