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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_pca_delete_ocsp

DestructiveIdempotent

Delete OCSP configuration from a CA and remove the OCSP URL from all certificates it issued. Set confirm=true to execute this destructive action.

Instructions

⚠️ Destructive: Delete OCSP configuration and remove the OCSP URL from all certificates issued by this CA. 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": {
      "caTag": "<caTag>"
    },
    "name": "ncloud_pca_delete_ocsp"
  }
}

Input Schema

NameRequiredDescriptionDefault
caTagYesCA tag value (required)
confirmNoMust be true to actually execute the destructive operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A4.5/5.0
Behavior5/5

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

The description adds significant behavioral context beyond the annotations: it discloses that the OCSP URL is removed from all certificates issued by the CA, which is a critical side effect. It also reinforces the confirm=true safeguard, making the destructive nature explicit.

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 a warning emoji and clear instruction. Every word earns its place, making it highly concise and well-structured.

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?

Given the tool's simplicity (2 params, no output schema), the description is complete: it covers purpose, destructive side effect, and the confirm requirement. The annotations cover idempotency, so no gaps remain.

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%, and the confirm parameter is already fully described in the schema. The description adds a minor reinforcement ('Set confirm=true to execute') but does not provide additional meaning for caTag beyond what the schema already states.

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), the resource (OCSP configuration), and the scope (removes the OCSP URL from all certificates issued by this CA). This is specific and distinguishes it from sibling tools like ncloud_pca_create_ocsp.

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 that this is a destructive operation and instructs the agent to set confirm=true to execute. It does not explicitly name alternatives or exclusions, but the context is sufficient for when to use this tool.

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