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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_postgresql_read_replica

Create a read replica for a Cloud DB for PostgreSQL instance to offload read traffic and enhance performance.

Instructions

Create a read replica for a 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_create_postgresql_read_replica"
  }
}

Input Schema

NameRequiredDescriptionDefault
subnetNoNoSubnet number for the read replica instance
cloudPostgresqlInstanceNoYesCloud PostgreSQL instance number to create read replica for
cloudPostgresqlServerNamePrefixNoServer name prefix for the read replica

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior2/5

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

With only a destructiveHint: false annotation (which is consistent with 'Create'), the description adds no additional behavioral context. It does not disclose whether the operation is asynchronous, how to track progress, or any side effects beyond creating a replica. The description does not contradict annotations, but it adds minimal value.

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, concise sentence with no wasted words. It effectively communicates the tool's purpose without verbosity or redundant phrasing.

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

Completeness2/5

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

For a create operation with no output schema, the description is incomplete. It does not mention what is returned on success, whether the operation is synchronous or asynchronous, or how to check the status. Given the lack of annotation coverage and output schema, the description fails to provide sufficient context for an agent to fully understand the tool's behavior.

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 covers 100% of parameters with clear descriptions (e.g., 'Cloud PostgreSQL instance number to create read replica for'), so the baseline is 3. The tool description itself adds no parameter-level meaning beyond what the schema already provides.

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 and resource: 'Create a read replica for a Cloud DB for PostgreSQL instance'. It specifies the exact action and the target resource, and the name aligns with sibling tools like ncloud_delete_postgresql_read_replica, distinguishing this creation action.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, such as needing an existing primary instance, nor does it contrast with creating a separate instance or using the delete replica tool. Usage is only implied by the name.

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