ncloud-mcp-server

ncloud_gtm_update_policy

Idempotent

Update an existing Global Traffic Manager policy to adjust load balancing, health checks, and resource groups for traffic distribution.

Instructions

Update an existing Global Traffic Manager policy

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": {
      "policyId": "<policyId>"
    },
    "name": "ncloud_gtm_update_policy"
  }
}

Input Schema

Name	Required	Description
`name`	No	Policy name
`lbType`	No	Load balancing type
`monitor`	No	Health check monitor configuration
`geoMapId`	No	Geo/CIDR Map ID
`policyId`	Yes	Policy ID to update
`resourceGroups`	No	Resource groups

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false, and the description adds no additional behavioral context. It does not disclose whether the update is partial (only provided fields are changed) or whether it replaces the entire policy configuration, which would be useful beyond the 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?

The description is a single, clear sentence with no redundant words. It is perfectly concise and front-loaded, efficiently stating the tool's purpose.

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

Completeness3/5

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

The schema is rich and comprehensively describes all parameters, and annotations cover the safety profile. The description is sufficient for a basic understanding but lacks context on scope boundaries (e.g., it does not clarify that this tool handles overall policy settings, not just resources or health checks), which is important given the numerous closely related sibling tools.

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 has 100% description coverage for all properties, so the schema already provides full parameter semantics. The tool description adds no extra parameter information, but given the high schema coverage, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the action (update) and the resource (existing Global Traffic Manager policy). It is specific and unambiguous, but it does not differentiate from related sibling tools like ncloud_gtm_update_policy_resources or ncloud_gtm_update_policy_health_check, which also update aspects of a GTM policy.

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 ncloud_gtm_update_policy_resources or ncloud_gtm_update_policy_health_check. It does not mention any prerequisites, such as needing an existing policy ID, or clarify whether this is for general policy settings only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server