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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_reboot_postgresql_server

Idempotent

Reboot a Cloud DB for PostgreSQL server instance to fix issues or apply configuration changes. Provide the instance number to restart.

Instructions

Reboot a Cloud DB for PostgreSQL server 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": {
      "cloudPostgresqlServerInstanceNo": "<cloudPostgresqlServerInstanceNo>"
    },
    "name": "ncloud_reboot_postgresql_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudPostgresqlServerInstanceNoYesCloud PostgreSQL server instance number to reboot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds no context about operational effects like temporary downtime, connection interruptions, or required permissions. For a disruptive action, this absence of disclosure is a gap.

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 zero waste. It conveys the essential information without any redundancy.

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 reboot operation with one parameter and solid annotations, the description is sufficient. Adding a note about the operational impact (e.g., brief downtime) would make it fully complete, but the low complexity warrants a high score.

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 schema fully describes the single parameter with 100% coverage, and the description adds no additional meaning beyond what the schema already provides. The baseline of 3 is appropriate since the schema does the heavy lifting.

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 action ('Reboot') and the specific resource ('Cloud DB for PostgreSQL server instance'), making it unambiguous and distinct from sibling reboot tools for other database types like MySQL, MSSQL, MongoDB, and Cache.

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, such as rebooting MySQL or regular servers. It lacks any context about prerequisites, use cases, or when this tool is the appropriate choice.

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