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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_login_keys

DestructiveIdempotent

Permanently delete one or more login keys from NCP Gov cloud. Requires confirmation (confirm=true) to execute.

Instructions

⚠️ Destructive: Permanently delete one or more login keys. Set confirm=true to execute.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyNameList": "<keyNameList>"
    },
    "name": "ncloud_delete_login_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
keyNameListYesList of login key names to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint, idempotentHint), the description adds the crucial behavioral detail that deletion is permanent and requires setting `confirm=true`, a non-obvious safeguard not conveyed by the annotations. This adds meaningful context without contradicting the 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 two sentences, front-loaded with a clear warning and a concise action statement, followed by the essential execution requirement. Every sentence earns its place with no redundant or filler content.

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 delete tool with two well-documented parameters, relevant annotations, and no output schema, the description sufficiently covers the destructive nature, the confirm gate, and the resource scope. It does not elaborate on side effects or prerequisites, but none are essential for this operation.

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%: both `confirm` and `keyNameList` already have descriptive schema text. The tool description only repeats the confirm requirement without additional parameter-level insights, so it adds no semantic value beyond the schema.

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 clearly states the tool's function: 'Permanently delete one or more login keys.' This uses a specific verb ('delete'), resource ('login keys'), and scope ('one or more'), which distinguishes it from sibling tools like ncloud_list_login_keys, ncloud_create_login_key, and ncloud_import_login_key.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for usage: it is a destructive operation requiring `confirm=true` to execute. It implies when to use (when deleting login keys) but does not explicitly reference alternatives or exclusion scenarios, so it falls short of a 5.

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