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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_network_interface

DestructiveIdempotent

Permanently deletes a specified network interface from Naver Cloud Platform Government Cloud. Requires confirmation to execute.

Instructions

⚠️ Destructive: Permanently delete a network interface. 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": {
      "networkInterfaceNo": "<networkInterfaceNo>"
    },
    "name": "ncloud_delete_network_interface"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
networkInterfaceNoYesNetwork interface number 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?

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds value by emphasizing permanence ('Permanently delete') and revealing the confirm=true guardrail, which is critical behavioral context beyond the annotations. 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, compact sentence with the destructive warning front-loaded using the ⚠️ symbol. Every element serves a purpose: it communicates the resource, the action, the permanence, and the required confirmation. No wasted words.

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?

This is a simple two-parameter destructive tool with no output schema. The description, combined with annotations and schema, covers the essential context: what is deleted, permanence, and the confirm flag requirement. It could potentially mention side effects like what happens to associated resources, but that is not necessary for such a focused delete 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%, with both parameters (confirm and networkInterfaceNo) already well-documented in the input schema. The description reinforces the confirm parameter's purpose but does not add meaning beyond what the schema provides, so a baseline score is appropriate.

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 action: 'Permanently delete a network interface.' This is a specific verb+resource combination that distinguishes it from sibling operations like create, attach, or detach network interfaces. The addition of 'Set confirm=true to execute' also clarifies the required execution guard.

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 clearly indicates this is for deleting a network interface and implies the usage context through the destructive warning and confirm requirement. It does not explicitly mention alternatives or when-not-to-use scenarios, but the clear delete semantics provide sufficient context for an agent to select it appropriately.

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