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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_globalcdn_request_purge

Purge Global CDN cache to invalidate whole content or specific files. Choose scope by domain or file list to refresh cached resources.

Instructions

Request a Global CDN cache purge (invalidation). Purge whole content or specific files. isWholeDomain/isWholePurge select scope.

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": {
      "cdnInstanceNo": "<cdnInstanceNo>",
      "isWholeDomain": "<isWholeDomain>",
      "isWholePurge": "<isWholePurge>"
    },
    "name": "ncloud_globalcdn_request_purge"
  }
}

Input Schema

NameRequiredDescriptionDefault
isWholePurgeYestrue: purge all files; false: only targetFileList
cdnInstanceNoYesGlobal CDN instance number to purge
isWholeDomainYestrue: purge across all domains; false: only domains in serviceDomainNameList
targetFileListNoSpecific file paths to purge (required when isWholePurge=false)
serviceDomainNameListNoService domain names to purge (required when isWholeDomain=false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

The annotations include destructiveHint=false, so the agent already knows this is not a destructive operation in the data-loss sense. The description adds that it purges whole or specific files via isWholeDomain/isWholePurge, but this is essentially parameter guidance. It does not disclose additional behavioral traits like asynchronous processing, propagation delay, or irreversibility beyond the basic 'purge' action.

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 two short sentences, front-loads the core action ('Request a Global CDN cache purge'), and wastes no words. The second sentence succinctly summarizes the two key boolean parameters, making it easy to scan.

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 there is no output schema, the description does not mention what the API returns (e.g., a purge request ID) or that the purge might be asynchronous and take time to propagate. While the operation is straightforward and the schema covers parameters, these missing operational details are clear gaps for an agent invoking the tool.

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%, with detailed descriptions for each parameter already present. The description adds minimal extra meaning beyond noting that isWholeDomain/isWholePurge select scope, which mostly restates schema information. 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 tool requests a Global CDN cache purge (invalidation), with a specific verb 'request', resource 'Global CDN cache', and scope ('whole content or specific files'). It explicitly mentions 'Global CDN', distinguishing it from the sibling tool 'ncloud_cdnplus_request_purge' for CDN+.

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?

The description prominently names 'Global CDN', making the intended context clear (use this for Global CDN cache purges). It does not explicitly list alternatives or exclusions, but the product-specific naming and sibling tool names provide sufficient differentiation for an agent to select this tool correctly.

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