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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_snapshots

Read-only

List block storage snapshot instances with optional filtering by snapshot numbers and pagination.

Instructions

List all block storage snapshot instances

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number for pagination
pageSizeNoPage size for pagination
blockStorageSnapshotInstanceNoListNoFilter by snapshot instance numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

The annotation readOnlyHint: true already declares the operation is read-only. The description adds no extra behavioral context such as pagination behavior, default page size, ordering, or whether all snapshots are returned. It simply restates the listing function without expanding on observable behavior.

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 with no filler. It is front-loaded and easy to parse, making every word earn its place.

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?

While the schema covers parameters and annotations cover safety, the description lacks any context about when to use this tool versus similar snapshot listing tools. It also omits mention of pagination or filtering capabilities, which are part of the tool's expected behavior. For a simple list tool this is adequate but not fully complete.

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?

All three parameters (pageNo, pageSize, blockStorageSnapshotInstanceNoList) have descriptions in the schema, achieving 100% coverage. The description itself does not elaborate on parameter meaning or usage, so it adds no extra semantics beyond what the schema already provides.

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 ('List') and the resource ('block storage snapshot instances'), making the tool's purpose immediately obvious. It also distinguishes itself from related tools like ncloud_list_nas_snapshots and ncloud_delete_snapshots by specifying the resource type.

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_list_nas_snapshots or ncloud_get_snapshot_detail. There is no mention of pagination or filtering use cases, leaving the agent without context for selecting this tool.

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