ncloud-gov-mcp-server

ncloud_list_servers

Read-only

Lists all server instances in the current region. Supports filtering by VPC number, instance numbers, and pagination.

Instructions

List all server 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_servers"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	No	Filter by VPC number
`pageNo`	No	Page number for pagination
`pageSize`	No	Page size for pagination
`serverInstanceNoList`	No	Filter by server instance numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description does not need to establish safety. It does add context by specifying 'current region,' which is useful scoping information. However, it does not disclose details about pagination behavior or return format, which would add value beyond the annotations.

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, tightly packed sentence that states exactly what the tool does. There is no redundancy or unnecessary filler.

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?

For a simple read-only list operation with all optional parameters documented in the schema, the description is sufficient. It could mention pagination or that it returns a list of server instances, but these are implied by the tool name and the parameter schema. The lack of an output schema increases the need for some return guidance, but the overall context is adequate.

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 each parameter (vpcNo, pageNo, pageSize, serverInstanceNoList) having a clear description. The tool description adds no additional parameter meaning, so the baseline 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'), identifies the resource ('server instances'), and scopes the operation ('in the current region'). This clearly distinguishes it from single-server actions like ncloud_get_server_detail or creation/management tools such as ncloud_create_server or ncloud_terminate_server.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention that for a single server one should use ncloud_get_server_detail, nor does it explain pagination or filtering options. The scope is limited to a single indicative sentence.

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

Deploy Server