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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mssql_products

Read-only

List available Cloud DB for MSSQL server product codes by providing an image product code, enabling quick selection of compatible configurations.

Instructions

List available Cloud DB for MSSQL server spec product codes

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": {
      "cloudMssqlImageProductCode": "<cloudMssqlImageProductCode>"
    },
    "name": "ncloud_get_mssql_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudMssqlImageProductCodeYesMSSQL image product code (from ncloud_get_mssql_image_products)

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 readOnlyHint annotation already covers the safe read-only nature of the operation. The description adds that it lists product codes but does not disclose additional behavioral traits such as pagination, filtering, or permissions. No contradiction with annotations.

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, succinct sentence that conveys the tool's purpose without unnecessary words. 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 list tool with one well-documented parameter and readOnlyHint, the description is sufficiently complete. It does not need to explain return values in detail, though mentioning the product code output is implicit in 'product codes.' The prerequisite relationship with image product codes is covered in the parameter description.

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 has one required parameter with a clear description indicating it comes from ncloud_get_mssql_image_products. Schema coverage is 100%, so the description does not need to add further parameter detail. The baseline 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 uses a specific verb 'List' and clearly identifies the resource as 'available Cloud DB for MSSQL server spec product codes.' This distinguishes it from sibling tools like ncloud_get_mysql_products or ncloud_get_mssql_image_products.

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: if you need MSSQL server spec product codes, use this tool. However, it does not explicitly state when to use it over alternatives or mention when not to use it. The context is clear but lacks direct guidance or exclusions.

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