Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425

ncloud_edge_create_edge

Create a Global Edge CDN edge by configuring origin type, service domain, protocol, and region; use dryRun to preview before actual creation.

Instructions

Create a new Global Edge CDN edge with origin, caching, and distribution settings. Use dryRun=true to preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dryRunNoIf true, returns a preview without actually creating the edge
edgeNameYesEdge name (3-35 chars, letters, numbers, '-', '_')
profileIdYesProfile ID to create the edge under
originPortNoOrigin port number
originTypeYesOrigin server type
regionTypeYesService area (KOREA, JAPAN, or GLOBAL)
originRegionNoOrigin region (required for OBJECT_STORAGE or LOAD_BALANCER)
protocolTypeYesService protocol type
originBucketNameNoOrigin bucket name (required for OBJECT_STORAGE)
certificateSlotIdNoCertificate slot ID (required for CUSTOM_DOMAIN with HTTPS)
serviceDomainNameNoDomain name (required for NCP_DOMAIN_CUSTOM or CUSTOM_DOMAIN)
serviceDomainTypeYesService domain type
originProtocolTypeNoOrigin protocol typeHTTP
originCustomLocationNoOrigin domain name (required for LOAD_BALANCER, API_GATEWAY, or CUSTOM)
Behavior3/5

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

Annotations include destructiveHint=false, indicating non-destructive behavior. The description adds the dryRun preview feature beyond annotations, but does not disclose other behavioral traits such as authentication needs, rate limits, or side effects. The added value is moderate.

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 concise: two sentences that front-load the main purpose and include a practical usage tip. No wasted words or redundant information.

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?

Given the complexity of 14 parameters with conditional requirements, the description is brief. It does not summarize parameter dependencies (e.g., required fields for different origin types) but the schema covers these details. The dryRun hint is valuable, but overall completeness for a complex creation tool is adequate.

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 description coverage is 100%, so the description does not need to explain individual parameters. It mentions the dryRun parameter, which adds slight value beyond the schema. 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 states a clear purpose: 'Create a new Global Edge CDN edge with origin, caching, and distribution settings.' It specifies the verb (Create), the resource (Global Edge CDN edge), and the scope, distinguishing it from sibling tools like ncloud_edge_list_edges or ncloud_edge_get_edge.

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 provides a usage hint: 'Use dryRun=true to preview without creating.' However, it does not explicitly state when to use this tool versus alternatives or include prerequisites. The usage context is implied by the tool name and description, but explicit guidance is minimal.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sjk4425/ncloud-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server