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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_mssql_config_groups

Read-only

List available MSSQL configuration groups for Cloud DB instances, enabling selection of pre-defined parameter sets for database setup.

Instructions

List available Config Groups for Cloud DB for MSSQL

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_list_mssql_config_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (KR, KRS). Defaults to current region.

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 annotation readOnlyHint=true already communicates the read-only, non-destructive nature. The description simply says 'List', which aligns with the annotation, but adds no further behavioral context such as pagination, filtering, or response details beyond the name.

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, concise sentence that precisely states the action and target resource. Every word is necessary, and there is no redundancy or filler.

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 list operation with one optional parameter and no output schema, the description is adequate. It could benefit from a brief note on what a Config Group represents or the return structure, but the minimal complexity means the current description is nearly 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?

The input schema has one optional parameter (regionCode) with a full description, providing 100% schema coverage. The tool description does not add additional parameter context, so the baseline 3 applies as the schema carries the meaning.

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 ('List') and identifies the resource ('Config Groups for Cloud DB for MSSQL'), clearly distinguishing it from sibling tools like ncloud_cdss_list_config_groups (for Kafka) and ncloud_list_cache_config_groups (for Cache). The product-specific name removes ambiguity.

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 its use: when you need to list Config Groups for Cloud DB for MSSQL. However, it does not explicitly state when to prefer this over alternatives or mention exclusions, leaving the guidance implicit.

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