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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_mssql_instance_detail

Read-only

Retrieve detailed configuration and status for a specific Cloud DB for MSSQL instance using its instance number, enabling quick verification and management of database resources.

Instructions

Get detailed information about a specific Cloud DB for MSSQL instance

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": {
      "cloudMssqlInstanceNo": "<cloudMssqlInstanceNo>"
    },
    "name": "ncloud_get_mssql_instance_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudMssqlInstanceNoYesCloud MSSQL instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior2/5

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

The readOnlyHint annotation already declares the tool read-only, and the description adds no behavioral context beyond that. It does not specify what 'detailed information' includes, any response format, or any additional side effects or prerequisites.

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 of nine words, front-loaded with the verb, and contains no superfluous content. Every word contributes to the meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and a read-only annotation, so a short description is acceptable. However, 'detailed information' is vague and with no output schema, the agent might not know what fields to expect. It covers the essential use case but lacks specificity about the response.

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 coverage is 100% with a clear description of the only parameter, so the description need not add parameter details. The tool description does not add meaning beyond the schema, but the baseline is met.

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 action ('Get detailed information') and the specific resource ('a specific Cloud DB for MSSQL instance'). The word 'specific' distinguishes it from list-type siblings, and the 'detailed' modifier indicates a detail-retrieval tool.

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 when you need details for a known MSSQL instance, but it does not explicitly mention alternatives or when not to use it. There is no guidance on first listing instances to obtain the required instance number.

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