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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_login_keys

Read-only

Lists all login keys in the current region. Supports pagination via page number and page size to manage large collections.

Instructions

List all login keys 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_login_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number for pagination
pageSizeNoPage size for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already covers the safe read-only nature. The description adds that it is region-scoped ('current region'), which is useful context. However, it does not disclose pagination behavior, response format, or any quota/limit considerations, so transparency is adequate but not enriched beyond the basics.

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 with zero wasted words. It effectively communicates the core purpose and scope.

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 operation with optional pagination and a readOnly hint, the description is reasonably complete. It specifies the resource, scope, and region. The absence of an output schema is acceptable for a standard list endpoint, though a note about default pagination or response structure could make it more thorough.

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 both pageNo and pageSize having clear descriptions for pagination. The tool description adds no additional meaning beyond what the schema already provides, so the baseline 3 applies.

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' and a clear resource 'login keys' with an explicit scope ('all' and 'current region'). This distinguishes it from sibling operations like create, import, delete login keys, and from service-specific list tools such as ncloud_hadoop_list_login_keys.

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?

Usage is implied (use when you need to list login keys), but there is no explicit guidance on when to prefer this over alternatives like ncloud_ses_get_login_keys or ncloud_hadoop_list_login_keys. The description does not provide exclusions or alternate tool mentions.

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