ncloud-gov-mcp-server

ncloud_gtm_create_geo_cidr_map

Create a Geo or CIDR map for Global Traffic Manager by defining zones, CIDR subnets, and geolocation mappings.

Instructions

Create a new Geo or CIDR map for Global Traffic Manager

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": {
      "name": "<name>",
      "mapType": "<mapType>",
      "detailedMapList": "<detailedMapList>"
    },
    "name": "ncloud_gtm_create_geo_cidr_map"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Map name
`mapType`	Yes	Map type
`detailedMapList`	Yes	Detailed map entries

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

The annotation destructiveHint=false is the only behavioral signal. The description adds no additional context such as idempotency, failure conditions on duplicate names, or whether the operation is synchronous. It does not contradict the annotation but also adds no value beyond it.

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 sentence that efficiently conveys the tool's purpose without any redundant or extraneous words. Every word contributes to the meaning.

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?

The schema fully documents the required parameters, and the description clearly states the action. Given the richness of the schema and the simplicity of a create operation, the description is largely complete. It lacks some behavioral details like return values or duplicate-name handling, but these are not essential for basic usage.

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 provides 100% description coverage for all parameters, including the mapType enum and the nested detailedMapList structure. The description adds no parameter-specific meaning beyond what the schema already supplies, so the baseline of 3 is appropriate.

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 ('Create') and the resource ('new Geo or CIDR map') within the context of Global Traffic Manager. This distinguishes it from sibling operations like list, get, update, and delete on the same resource.

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 guidance is provided on when to use this tool versus alternatives. It does not mention that it should be used only for creating new maps, nor does it reference the update or delete siblings. There are no prerequisites or special cases described.

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

Deploy Server