ncloud-mcp-server

ncloud_get_postgresql_products

Read-only

Retrieve Cloud DB for PostgreSQL server spec product codes by entering a PostgreSQL image product code to identify available options.

Instructions

List available Cloud DB for PostgreSQL server spec product codes for a given image product code

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": {
      "cloudPostgresqlImageProductCode": "<cloudPostgresqlImageProductCode>"
    },
    "name": "ncloud_get_postgresql_products"
  }
}

Input Schema

Name	Required	Description	Default
`regionCode`	No	Region code (e.g. KR, SGN, JPN). Defaults to current region.
`cloudPostgresqlImageProductCode`	Yes	PostgreSQL image product code (from ncloud_get_postgresql_image_products)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations declare readOnlyHint: true, and the description's use of 'List' is consistent. The description adds no behavioral details beyond the annotation, such as side effects, rate limits, or authentication needs, but it does not contradict 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, well-structured sentence that immediately conveys the action and scope. No extraneous words or unnecessary details.

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 (listing product codes), the description adequately covers the purpose and dependency on the image product code. It does not mention the optional regionCode parameter or output format, but these are detailed in the schema.

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 description coverage is 100%, with both parameters already described in the schema. The tool description adds no new meaning or syntax details beyond what the schema provides, so the baseline score of 3 applies.

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 resource (product codes for PostgreSQL server specs), and specifies the condition (for a given image product code). It is specific and distinguishes this tool from siblings like ncloud_get_mysql_products or ncloud_get_mssql_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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites like obtaining the image product code from ncloud_get_postgresql_image_products. However, the input schema includes that context for the required parameter.

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

Deploy Server