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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_postgresql_read_replica

DestructiveIdempotent

Delete a Cloud DB for PostgreSQL Read Replica instance. Set confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Delete a Cloud DB for PostgreSQL Read Replica instance. Set confirm=true to execute.

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": {
      "cloudPostgresqlReadReplicaInstanceNo": "<cloudPostgresqlReadReplicaInstanceNo>"
    },
    "name": "ncloud_delete_postgresql_read_replica"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
cloudPostgresqlReadReplicaInstanceNoYesCloud PostgreSQL Read Replica instance number to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already mark destructiveHint=true and idempotentHint=true. The description adds the confirm=true requirement, but this is also documented in the schema parameter description, so it adds minimal new behavioral context beyond annotations.

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?

Single sentence with a warning prefix; highly efficient and front-loaded. Every word adds value, and the structure is immediately clear.

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 simple delete operation with complete schema and annotations, the description covers the essential action and safety gate. It doesn't mention irreversibility or prerequisites, but annotations mitigate this and no output schema is expected.

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?

Both parameters are fully described in the schema (100% coverage). The description does not add any parameter semantics beyond stating the confirm requirement, which is already in the schema.

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 a specific verb ('Delete') and resource ('Cloud DB for PostgreSQL Read Replica instance'), clearly distinguishing it from deleting the primary PostgreSQL instance or other resources. It is concise and unambiguous.

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?

No explicit guidance on when to use this tool versus alternatives such as ncloud_delete_postgresql_instance or ncloud_create_postgresql_read_replica. The context is implied but no alternatives or exclusions are mentioned.

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