ncloud-gov-mcp-server

ncloud_list_load_balancers

Read-only

List load balancer instances in the current region and filter by VPC, type, network, or instance numbers to identify the resources you need.

Instructions

List all load balancer 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_load_balancers"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	No	Filter by VPC number
`pageNo`	No	Page number for pagination
`pageSize`	No	Page size for pagination
`loadBalancerType`	No	Filter by LB type (APPLICATION, NETWORK, NETWORK_PROXY)
`loadBalancerNetworkType`	No	Filter by network type (PUBLIC, PRIVATE)
`loadBalancerInstanceNoList`	No	Filter by load balancer 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?

The annotations provide readOnlyHint: true, so the description correctly implies a safe read operation. It adds the useful scope 'current region' but fails to disclose that pagination parameters (pageNo, pageSize) exist, which means 'all' may require multiple calls. No contradiction with annotations, but limited behavioral depth beyond the annotation.

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, front-loaded sentence with no filler or redundancy. Every word contributes to understanding the tool's 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?

For a simple list tool with a readOnly annotation, full schema coverage of all parameters, and clear naming, the description is mostly complete. However, it does not mention the potential need for pagination when saying 'all', nor does it describe the return format (though there is no output schema). This small gap prevents a perfect score.

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 6 parameters are described in the input schema with 100% coverage, so the schema carries the full parameter meaning. The description adds no extra information about filters or pagination, earning the baseline score of 3 for a description that does not actively help explain parameters.

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 'List all load balancer instances in the current region' uses a specific verb ('List'), resource ('load balancer instances'), and scope ('current region'), clearly distinguishing it from siblings like get_load_balancer_detail, create_load_balancer, or delete_load_balancers. The word 'all' also signals this is a broad list operation.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention that for a single load balancer's details one should use ncloud_get_load_balancer_detail, or that ncloud_list_lb_listeners is for listeners. The usage context is only implied by the verb 'list' and the resource name.

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

Deploy Server