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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_log_servers

Read-only

Lists servers eligible for log collection in Cloud Log Analytics and reports per-server collection status so you can select targets for logging setup.

Instructions

List servers eligible for log collection in Cloud Log Analytics (includes per-server collection status).

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

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (1-100, default 1)
pageSizeNoPage size (10-100, default 10)
platformNoPlatform (default vpc)
regionCodeNoRegion code as a lowercase path segment (kr, jpn, sgn, uswn, den). Default: the client's active region

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / regionCode / description
      Previous value: -"Region code (kr, sgn, jpn). Default kr"New value: +"Region code as a lowercase path segment (kr, jpn, sgn, uswn, den). Default: the client's active region"
  2. First observedv1.10.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds a small behavioral detail (results include per-server collection status), but says nothing about pagination, default result size, or whether it is region/platform scoped.

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?

A single sentence, front-loaded with the verb and scope, with the parenthetical adding useful output context. No waste.

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 paginated list tool with a fully documented schema and readOnlyHint annotation, the description is almost sufficient. The main gap is the absence of any note about result volume or that paging defaults apply, which is minor.

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%, so all four parameters (pageNo, pageSize, platform, regionCode) are already documented with defaults and ranges in the schema. The description adds no syntax or format detail beyond that, making the baseline 3 appropriate.

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?

States a specific verb (List) and a well-scoped resource (servers eligible for log collection in Cloud Log Analytics), plus a content hint that output includes per-server collection status. This scope qualifier distinguishes it from the generic ncloud_list_servers sibling, though it does not explicitly name that sibling.

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 when-to-use guidance, prerequisites, or alternatives are given. The description never routes the agent toward or away from related tools such as ncloud_set_server_log_collection or ncloud_search_logs, so the agent must infer usage from the name alone.

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