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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_pca_update_ca

Idempotent

Update a Certificate Authority (CA) status to ACTIVE, DEACTIVATED, or DESTROYING. Set to DESTROYING to permanently delete the CA and all sub-CAs after 72 hours, irreversible.

Instructions

⚠️ Destructive: Update CA status (ACTIVE, DEACTIVATED, or DESTROYING). Setting to DESTROYING will permanently delete the CA and all sub-CAs after 72 hours. This action is irreversible.

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>",
      "status": "<status>"
    },
    "name": "ncloud_pca_update_ca"
  }
}

Input Schema

NameRequiredDescriptionDefault
caTagYesCA tag value
statusYesNew CA status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior1/5

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

The description warns that setting DESTROYING will permanently delete the CA after 72 hours and is irreversible, which is useful behavioral context. However, this directly contradicts the annotation destructiveHint: false. The description clearly signals a destructive action while the annotation denies it, creating a serious inconsistency.

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 three short sentences, warning first, then explaining the destructive behavior and irreversibility. Every sentence contributes essential information with no fluff or repetition.

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

Completeness3/5

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

The tool is simple with only two fully documented parameters and no output schema, so the description covers the most critical aspect (DESTROYING consequences). However, the annotation contradiction undermines completeness by giving an agent contradictory safety signals, and the effects of DEACTIVATED status are not described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes both parameters with 100% coverage. The description adds extra meaning for the status parameter by explaining the consequence of DESTROYING, which goes beyond the schema's enum listing. No additional info is provided for caTag, but the schema fully documents it.

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 verb ('Update'), resource ('CA status'), and the valid statuses (ACTIVE, DEACTIVATED, DESTROYING). It is specific enough to distinguish from sibling tools like ncloud_pca_delete_ca.

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

Usage Guidelines3/5

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

The description implies when to use this tool (to change a CA's status) and warns about DESTROYING, but it does not explicitly contrast with alternatives (e.g., ncloud_pca_delete_ca) or state when NOT to use it. The guidance is helpful but not fully explicit.

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