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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_add_postgresql_databases

Add one or more databases to a Cloud DB for PostgreSQL instance by providing the instance number and a list of database names.

Instructions

Add databases to 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>",
      "cloudPostgresqlDatabaseList": "<cloudPostgresqlDatabaseList>"
    },
    "name": "ncloud_add_postgresql_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudPostgresqlInstanceNoYesCloud PostgreSQL instance number
cloudPostgresqlDatabaseListYesList of databases to add

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already provide destructiveHint=false, which matches the additive operation. The description adds that it targets a Cloud DB for PostgreSQL instance and supports a list of databases, but does not disclose behavior such as duplicate handling, prerequisite instance states, or idempotency. This is adequate but minimal given annotation coverage.

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 filler or redundant information. It is front-loaded and immediately understandable.

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 two-parameter mutation with full schema coverage and a non-destructive annotation, the description plus schema provides sufficient information for correct invocation. It omits details about return values or constraints, but these are not critical for a straightforward add 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?

Schema descriptions cover 100% of the parameters ('Cloud PostgreSQL instance number' and 'List of databases to add'), so the description does not need to add parameter-level details. The phrase 'Add databases' aligns with the array parameter but provides no additional semantic value beyond 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 ('Add') and a specific resource ('databases to a Cloud DB for PostgreSQL instance'), clearly distinguishing it from siblings like ncloud_add_postgresql_users and ncloud_delete_postgresql_databases. It precisely states what the tool does.

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 implies the usage context (when you need to add databases to a PostgreSQL instance) but does not provide explicit when-to-use/when-not-to-use guidance or mention alternatives. It is self-evident from the operation name but lacks explicit directional guidance.

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