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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_nas_volumes

Read-only

List all NAS volume instances in a specified region, with optional filters for zone, protocol, and instance numbers to manage storage resources.

Instructions

List all NAS volume instances in the current region

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_nas_volumes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number for pagination
pageSizeNoPage size for pagination
zoneCodeNoZone code (e.g. KR-1, KR-2)
regionCodeNoRegion code (e.g. KR, SGN, JPN)
nasVolumeInstanceNoListNoFilter by NAS volume instance numbers
volumeAllotmentProtocolTypeCodeNoVolume protocol type code (NFS or CIFS)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description adds minimal value. It does mention 'current region' as a behavioral context, but no additional details about auth needs, rate limits, or data scope beyond that.

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 clear sentence with 8 words. There is no wasted text; it is front-loaded and easy to parse.

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?

Despite having no output schema, the description does not hint at return values or pagination. However, the schema covers parameters well. The description is adequate for a simple list tool but lacks some completeness for the 6 optional parameters.

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% (all 6 parameters have descriptions). The tool description does not add any extra meaning beyond what is already in the schema, so baseline score 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 uses a specific verb ('List') and resource ('NAS volume instances'), and clarifies scope ('in the current region'). It is distinct from sibling tools like ncloud_get_nas_volume_detail.

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?

No explicit guidance on when to use this tool versus alternatives such as ncloud_get_nas_volume_detail. The description only states what it does, not when it should be preferred.

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