Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_serverless_update_config

Idempotent

Update MySQL cluster configuration parameters; use dryRun to preview and applyWithoutRestart=false to allow non-dynamic parameters with a restart.

Instructions

Change DB parameters (PATCH /mysql/v1/clusters/{clusterName}/config, merge-patch → 202 Operation). applyWithoutRestart defaults to TRUE here (the API default is false = DB restart); with true, non-dynamic parameters are rejected with 400 — set applyWithoutRestart=false to accept a restart. Use dryRun=true to preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNo
parametersYesParameter name → value (strings)
clusterNameYesCluster name (3-30 chars, lowercase letters/digits/'-', no leading or trailing '-'; immutable after creation)
applyWithoutRestartNotrue (tool default) = only dynamic parameters, no restart; false = allow non-dynamic parameters, the DB restarts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.7/5.0
Behavior5/5

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

Discloses important behaviors beyond annotations: the default override for applyWithoutRestart (differs from API default), the 400 rejection for non-dynamic parameters, and dryRun for preview. Does not contradict the idempotent/destructive hints.

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, dense sentence that front-loads the purpose and packs in essential behavior. No fluff; every clause adds value.

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

Completeness5/5

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

Given the complexity (nested parameters, two boolean toggles), the description covers the key operational aspects: what it does, the applyWithoutRestart tradeoff, and dryRun. No output schema exists, but the 202 Operation hint is provided. Complete enough for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already documents each parameter well (high coverage). The description adds critical semantics: explains the interaction between applyWithoutRestart and parameter types, and the dryRun preview effect, which goes beyond simple field descriptions.

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?

Clearly states the action ('Change DB parameters') and the resource (cluster config via PATCH endpoint). It is specific and distinguishable from read-only siblings like ncloud_serverless_get_config or ncloud_serverless_list_config_parameters.

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

Usage Guidelines4/5

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

Provides clear behavioral context (applyWithoutRestart semantics, dryRun preview) but does not explicitly mention alternatives or exclusions. The description implies when to use it (for config changes) without saying when not to.

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