ncloud-gov-mcp-server

ncloud_pca_get_ca_crl

Read-only

Get the Certificate Revocation List (CRL) for a private CA in PEM format to verify revoked certificates.

Instructions

Get the CRL (Certificate Revocation List) of a Private CA in PEM format.

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_get_ca_crl"
  }
}

Input Schema

Name	Required	Description	Default
`caTag`	Yes	CA tag value

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds the output format (PEM), which is useful but minimal. It does not disclose additional behavioral traits such as error handling, rate limits, or whether the CA must exist. With annotations present, the bar is lower, and the description meets the minimum by not contradicting the read-only nature.

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 is front-loaded with the action ('Get') and includes the key detail (PEM format). 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?

For a simple tool with one parameter, full schema coverage, and a readOnly annotation, the description is adequate. It specifies the output format (PEM) even though there is no output schema, covering the most critical return detail. It does not explain the response structure or error cases, but for such a focused retrieve operation, this is acceptable.

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 caTag described as 'CA tag value'. The description does not add extra meaning beyond the schema, but since the schema fully documents the parameter, the baseline of 3 applies.

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 tool gets the CRL of a Private CA in PEM format, using a specific verb ('Get') and resource ('CRL of a Private CA'). This distinguishes it from sibling tools like ncloud_pca_get_crl_config (configuration) and ncloud_pca_get_ca_chain (chain).

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention when to prefer this over ncloud_pca_get_crl_config or ncloud_pca_rotate_crl, nor does it state any exclusions or prerequisites. The usage context is implied but not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server