Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_delete_certificate

DestructiveIdempotent

Permanently delete a registered SSL certificate after verifying it is not used by Load Balancer, CDN+, or Global Edge. Requires confirmation to execute.

Instructions

⚠️ Destructive: Permanently delete a registered certificate. Ensure it is not in use by any Load Balancer, CDN+, or Global Edge. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true to actually execute the destructive operation
certificateNoYesCertificate number to delete (from ncloud_list_certificates)
certificateNameYesCertificate name (must match exactly for verification; older certificates may have up to 30 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.16.0
    • changedInput schema / properties / certificateName / description
      Previous value: -"Certificate name (must match exactly for verification)"New value: +"Certificate name (must match exactly for verification; older certificates may have up to 30 chars)"
    • addedInput schema / properties / certificateName / minLength
      Added value: +1
  2. First observedv1.10.1

TDQS

A4.5/5.0
Behavior5/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 the permanent nature of deletion, the confirmation requirement, and the dependency check, which is meaningful context beyond 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?

Two concise sentences, with the destructive warning front-loaded and no unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive delete tool with no output schema, the description covers purpose, preconditions, confirmation, and dependency checks. An agent has enough to safely invoke it.

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%, so all parameters are already described. The description restates confirm=true and mentions the certificate source but adds no new semantic detail 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 states a specific verb and resource: 'Permanently delete a registered certificate.' The mention of Load Balancer, CDN+, and Global Edge dependencies helps distinguish this from other certificate deletion tools like ncloud_edge_delete_certificate.

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?

It provides explicit preconditions: ensure the certificate is not in use by Load Balancer, CDN+, or Global Edge, and set confirm=true to execute. However, it does not explicitly name alternative tools or conditions for choosing another deletion method.

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