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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_monitor_group

Read-only

Retrieve detailed information about a Cloud Insight monitoring target group by providing its ID, enabling inspection of monitoring configurations.

Instructions

Get detailed information about a specific Cloud Insight monitoring target 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": {
      "monitorGroupId": "<monitorGroupId>"
    },
    "name": "ncloud_get_monitor_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
monitorGroupIdYesMonitor group ID to retrieve details for

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?

The description aligns with the readOnlyHint annotation, so no contradiction. However, it adds little beyond the annotation: it only clarifies the resource type. It doesn't describe what 'detailed information' includes, authentication needs, or any limitations, but the annotation covers the safety profile.

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?

A single clear sentence conveys the essential purpose without any filler or redundancy. It is front-loaded and easy to parse.

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 get-by-ID tool with one parameter, readOnlyHint annotation, and no output schema, the description adequately conveys the core action. It lacks specifics about the return content but the tool is low-complexity, so the description is reasonably complete.

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% for the single required parameter monitorGroupId. The description does not add additional meaning about the parameter format, source, or constraints. Baseline 3 is appropriate since the schema fully documents the parameter.

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 clearly states the verb (Get), resource (specific Cloud Insight monitoring target group), and scope (detailed information). It distinguishes from sibling tools like ncloud_list_monitor_groups (which lists groups) and ncloud_get_rules_by_monitor_group (which retrieves 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 implies when to use it: to fetch details of a single monitor group by ID. It does not explicitly name alternatives, but the word 'specific' indicates a contrast with listing tools. No exclusions or when-not-to-use guidance is given.

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