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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_mssql_character_sets

Read-only

Find supported character sets for Cloud DB for MSSQL, enabling you to configure the correct encoding for your database.

Instructions

List available character sets 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_character_sets"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionCodeNoRegion code (e.g. KR, SGN, JPN). Defaults to current region.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

The description is consistent with the readOnlyHint annotation. However, it adds no additional behavioral information beyond the annotation. For a read-only list operation, the minimal disclosure is acceptable, but there is no mention of response format, pagination, or any side effects.

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 sentence that directly states the tool's purpose without any extraneous information. It is concisely front-loaded and every word earns its place.

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 simplicity of the tool (one optional parameter, no output schema, read-only), the description is largely complete. It conveys the core action and resource. However, a brief note about the return value (e.g., list of character set names) would improve completeness, but it is not essential.

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 only parameter (regionCode) is fully documented in the input schema (100% coverage). The description does not add further meaning beyond the schema. With high schema coverage, the baseline score of 3 is appropriate.

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 'List' and the resource 'available character sets for Cloud DB for MSSQL'. It specifies the exact scope (MSSQL character sets) and distinguishes this tool from sibling list tools (e.g., ncloud_list_mssql_instances, ncloud_list_mssql_backups).

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 does not provide explicit guidance on when to use this tool versus alternatives. The implied usage is to retrieve character sets for MSSQL, but no exclusions or alternative tools are mentioned. The simple nature of the tool partially mitigates this gap.

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