ncloud-gov-mcp-server

ncloud_get_mysql_instance_detail

Read-only

Retrieve detailed information about a specific Cloud DB for MySQL instance by providing its instance number. Use this to inspect configuration, status, and connection details for that database instance.

Instructions

Get detailed information about a specific Cloud DB for MySQL 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": {
      "cloudMysqlInstanceNo": "<cloudMysqlInstanceNo>"
    },
    "name": "ncloud_get_mysql_instance_detail"
  }
}

Input Schema

Name	Required	Description	Default
`cloudMysqlInstanceNo`	Yes	Cloud MySQL instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

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 indicates a read-only operation, and the description's verb 'Get' is consistent. No additional behavioral context is provided, such as the return structure, any pagination, or permission requirements, so the description adds little beyond the annotation.

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, front-loaded sentence with a clear verb and resource. It contains zero waste or redundant phrasing.

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?

The tool is simple: one required parameter, no output schema, and read-only annotation. The description adequately conveys the purpose, though it does not enumerate what 'detailed information' includes. For a get-by-id tool, this is mostly sufficient.

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 includes the required parameter cloudMysqlInstanceNo with a clear description 'Cloud MySQL instance number to query', giving 100% schema coverage. The description itself does not add further meaning to the parameter, so 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 the specific verb 'Get' and clearly identifies the resource as 'detailed information about a specific Cloud DB for MySQL instance'. This distinguishes it from the sibling list tool ncloud_list_mysql_instances and from detail tools for other database types like ncloud_get_postgresql_instance_detail.

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?

No explicit when-to-use or alternative tool is referenced, but the word 'specific' versus the sibling list tool implies this is for retrieving details of a single instance. The description does not name ncloud_list_mysql_instances as the alternative for enumerating instances, so guidance is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server