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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_public_ip

DestructiveIdempotent

Delete a public IP instance on NCP Gov Cloud. Requires confirm=true to execute the destructive operation.

Instructions

⚠️ Destructive: Delete a public IP instance. 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": {
      "publicIpInstanceNo": "<publicIpInstanceNo>"
    },
    "name": "ncloud_delete_public_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
publicIpInstanceNoYesPublic IP instance 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 the description reinforces this with a warning. It adds important behavioral context: the confirm parameter must be true to actually execute, preventing accidental deletions. This goes beyond the structured annotation information.

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, concise sentence that front-loads the critical warning and action. It includes no filler and is immediately scannable.

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 operation with annotations covering destructive and idempotent behavior, the description is sufficient. It explains the resource and the confirmation requirement. The lack of an output schema is acceptable given the straightforward nature of the 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?

The schema already describes both parameters with 100% coverage. The description reiterates the confirm parameter's requirement ('Set confirm=true to execute') but does not add additional semantic value beyond what the schema provides.

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: 'Delete a public IP instance.' It uses a specific verb and resource, distinguishing it from other delete tools and making the tool's purpose immediately obvious.

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 on how to use the tool ('Set confirm=true to execute'), which is essential for safe execution. It implicitly conveys when to use this tool (to delete a public IP) without mentioning alternatives, but the instruction is explicit enough for an agent.

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