ncloud-gov-mcp-server

ncloud_list_nas_snapshots

Read-only

List all snapshots for a specific NAS volume instance on Naver Cloud Platform Government Cloud, with pagination support for browsing large snapshot sets.

Instructions

List snapshots for a NAS volume instance

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": {
      "nasVolumeInstanceNo": "<nasVolumeInstanceNo>"
    },
    "name": "ncloud_list_nas_snapshots"
  }
}

Input Schema

Name	Required	Description
`pageNo`	No	Page number for pagination
`pageSize`	No	Page size for pagination
`nasVolumeInstanceNo`	Yes	NAS volume instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

The readOnlyHint annotation already communicates the safe read-only nature. The description adds a scoping context (NAS volume instance) but does not disclose other behavioral traits such as pagination behavior, sorting, or response structure. It is consistent with the annotation, with no contradiction.

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, concise sentence that contains no redundant information. Every word contributes to the stated purpose.

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?

Given the simplicity of the tool, the fully described parameters, and the readOnlyHint annotation, the description is sufficient for initial selection and invocation. However, it does not mention pagination behavior or return value structure, which would be helpful in the absence of an output schema.

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 coverage is 100% and each parameter, including pageNo, pageSize, and nasVolumeInstanceNo, already has a descriptive schema entry. The description does not add additional parameter-level meaning beyond what is provided in the schema.

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 uses the specific verb 'List' and clearly identifies the resource as 'snapshots for a NAS volume instance'. This distinguishes it from generic snapshot listers and NAS snapshot create/delete tools.

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 implies when to use the tool (to list snapshots of a NAS volume), but it does not explicitly mention alternatives, prerequisites, or when not to use it. No additional guidance beyond the basic purpose is provided.

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

Deploy Server