ncloud-mcp-server

ncloud_list_route_tables

Read-only

List route tables in the current region using optional filters for VPC, name, route table numbers, or subnet type to locate routing configurations.

Instructions

List all route tables 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_route_tables"
  }
}

Input Schema

Name	Required	Description
`vpcNo`	No	Filter by VPC number
`routeTableName`	No	Filter by route table name
`routeTableNoList`	No	Filter by route table numbers
`supportedSubnetTypeCode`	No	Filter by supported subnet type (PUBLIC, PRIVATE)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The readOnlyHint annotation covers the safety profile, and the description adds the 'current region' scoping detail. However, it does not disclose other behavioral traits such as response format, pagination, or that filtering parameters are available.

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 succinct sentence that conveys the core purpose without unnecessary words. It is easily parsed and front-loaded.

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?

For a list tool with no output schema, the description is minimal. It does not mention that results can be filtered, what fields are returned, or any limitations. While the schema provides parameter details, the description alone leaves some gaps for an agent deciding on invocation.

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 coverage is 100% with clear descriptions for all four parameters. The description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (List), the resource (route tables), and the scope (current region). It is distinct from the related 'get_route_table_detail' and 'get_routes' tools, though it does not explicitly contrast with them.

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 alternative route table tools (e.g., ncloud_get_route_table_detail, ncloud_get_routes). The description does not mention filter usage, prerequisites, or exclusions.

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

Deploy Server