ncloud-gov-mcp-server

ncloud_get_postgresql_instance_detail

Read-only

Fetch detailed configuration, status, and resource specifications for a specific Cloud DB for PostgreSQL instance by providing its instance number.

Instructions

Get detailed information about a specific Cloud DB for PostgreSQL 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": {
      "cloudPostgresqlInstanceNo": "<cloudPostgresqlInstanceNo>"
    },
    "name": "ncloud_get_postgresql_instance_detail"
  }
}

Input Schema

Name	Required	Description	Default
`cloudPostgresqlInstanceNo`	Yes	Cloud PostgreSQL instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already discloses that this is a safe read operation, and the description's 'Get' wording is consistent with that. The description adds no further behavioral context (e.g., what detailed information is returned), but the annotation covers the key safety dimension.

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 no filler. Every word contributes to conveying the tool's purpose, making it highly efficient and appropriately sized for a simple get-detail operation.

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 one-parameter, read-only detail lookup, the description is sufficiently complete. It clearly identifies the action and target resource, and the readOnlyHint annotation plus fully documented parameter reduce ambiguity. The absence of an output schema is not a significant gap for this simple operation.

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 fully covers the only parameter (cloudPostgresqlInstanceNo with description 'Cloud PostgreSQL instance number to query'). The tool description adds no additional semantic value for the parameter, so a baseline score of 3 is appropriate given the 100% schema description coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Get' with a clear resource: 'detailed information about a specific Cloud DB for PostgreSQL instance.' It appropriately contrasts with sibling list tools by emphasizing a specific instance, though it does not explicitly name alternative tools.

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?

Usage is implied: use this when you need details about one instance, as opposed to listing instances. No explicit when-to-use or why-this-over-alternatives guidance is provided, but the name and phrasing make the intended context reasonably clear.

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

Deploy Server