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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_gtm_list_geo_cidr_maps

Read-only

List Global Traffic Manager geo and CIDR maps with pagination to retrieve Naver Cloud GTM routing information.

Instructions

List Global Traffic Manager Geo and CIDR maps with optional pagination

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (0-based, default: 0)
sizeNoNumber of items per page (default: 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

The annotation readOnlyHint=true already covers the operation's safety, and the description adds the pagination behavior. It does not disclose return format or ordering, but for a simple list operation with read-only annotations, this is adequate. No contradiction with 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 front-loaded sentence that directly states the action and resource. No filler words; every term (List, Global Traffic Manager, Geo and CIDR maps, optional pagination) is informative.

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 read-only list tool with two optional parameters, the description plus schema provides a complete operational picture. However, the lack of an output schema and any mention of response details means the agent must infer what fields are returned, though this is typical for list operations.

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?

Both parameters are fully documented in the schema with defaults (page=0, size=20), so the description's mention of 'optional pagination' adds little. The description does not provide additional context beyond the schema's property descriptions.

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 the specific verb 'List' and identifies the resource as 'Global Traffic Manager Geo and CIDR maps', clearly stating the operation. It distinguishes from sibling tools like ncloud_gtm_get_geo_cidr_map_detail, which retrieves a single map, and create/update/delete tools, making the purpose unambiguous.

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?

The description implies usage for enumerating Geo and CIDR maps but does not explicitly contrast with alternatives or state when to use pagination. No exclusions or prerequisites are mentioned, leaving the agent to infer from the tool name and sibling context.

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