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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_search_metric_list

Read-only

Search available monitoring metrics for a product in Cloud Insight by providing the product key (cw_key) to retrieve the metric list.

Instructions

Search available monitoring metrics for a specific product in Cloud Insight.

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>"
    },
    "name": "ncloud_search_metric_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
prodKeyYesProduct key (cw_key) to search metrics 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?

Annotations already indicate readOnlyHint=true, and the description's 'Search' aligns with that. The description adds context that this is a discovery operation for a specific product, which is helpful. However, it doesn't disclose additional behavioral traits such as whether the metric list is static, whether pagination is used, or how results are formatted.

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, focused sentence that communicates the core function without any filler. It is front-loaded with the verb and resource, making it easy to scan and quickly understand the tool's purpose.

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 listing tool with one parameter and a read-only annotation, the description is largely sufficient. It could be improved by noting that the returned metric identifiers are likely used with query_monitoring_data, but given the low complexity and structured schema, it is complete enough for most selection scenarios.

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 schema provides a clear description for the only parameter, prodKey, with 100% coverage. The description adds no extra parameter information, so the agent relies solely on the schema. Baseline 3 is appropriate since the schema carries the semantic load.

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?

Description clearly states the verb 'search' and the resource 'available monitoring metrics' with a specific scope ('for a specific product in Cloud Insight'). It distinguishes itself from sibling tools that manage clusters, source code, or query monitoring data, making the tool's purpose unmistakable.

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 use when you need to discover metrics for a product, but it does not provide explicit alternatives or exclusionary guidance. It doesn't mention how this relates to other monitoring tools like query_monitoring_data, so the agent is left without clear 'when-to-use-this-vs-that' information.

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