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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_nas_volume_detail

Read-only

Query a specific NAS volume instance by its number to retrieve detailed configuration, status, and metadata.

Instructions

Get detailed information about a specific 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_get_nas_volume_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
nasVolumeInstanceNoYesNAS volume instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.3/5.0
Behavior2/5

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

The readOnlyHint annotation indicates a safe read operation, but the description adds no behavioral context beyond that. It does not disclose error behavior, response structure, or any additional operational characteristics.

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, front-loaded sentence with no unnecessary words. It is appropriately concise for the simplicity of the tool.

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 simple one-parameter read-only nature, the description is functional but sparse. It does not explain what 'detailed information' includes, how to obtain the instance number, or what the response looks like, which limits completeness.

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?

The schema provides 100% coverage with a clear description of 'nasVolumeInstanceNo' as the NAS volume instance number to query. The description adds no extra meaning beyond the schema, so a 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 clearly states the tool gets detailed information about a specific NAS volume instance, using a specific verb ('Get') and resource ('NAS volume instance'). It distinguishes itself from list tools like ncloud_list_nas_volumes by emphasizing a single instance.

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?

No explicit usage guidance is provided. The description does not mention when to use this tool versus alternatives (e.g., list first, then get details), nor does it state any prerequisites or context for use.

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