ncloud-gov-mcp-server

ncloud_pca_issue_end_cert

Issue a new end-entity certificate from a CA, returning the private key, certificate, and CA chain. Specify CA tag and common name, with optional SANs, key type, and validity period.

Instructions

Issue a new end-entity certificate from a CA. Returns private key, certificate, and CA chain.

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>",
      "commonName": "<commonName>"
    },
    "name": "ncloud_pca_issue_end_cert"
  }
}

Input Schema

Name	Required	Description
`ip`	No	IP SANs (IP address format)
`caTag`	Yes	CA tag value of the issuing CA
`period`	No	Validity period in days (1-3650) or 'MAX'
`altName`	No	DNS/Email SANs
`country`	No	Country code (ISO 3166-1 alpha-2)
`keyType`	No	Key type for the certificate
`locality`	No	City name (0-128 chars)
`commonName`	Yes	Common Name (1-64 chars)
`organization`	No	Organization name (0-64 chars)
`stateProvince`	No	State/Province (0-128 chars)
`streetAddress`	No	Street address (0-128 chars)
`organizationUnit`	No	Organization unit (0-128 chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With empty annotations, the description carries the burden. It discloses the outputs (private key, certificate, CA chain) but does not mention side effects, required permissions, security implications, or whether issuance is reversible. This is minimal but non-trivial.

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 two concise sentences with no filler, front-loading the core purpose and key outputs.

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?

For a 12-parameter tool with no output schema, the description provides the core purpose and returns a brief list of outputs, but it omits return format, prerequisites, and error behavior. The schema compensates for parameters, so the description is moderately complete.

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 input schema provides 100% coverage with useful descriptions for all 12 parameters, including an enum for keyType. The description adds no parameter-specific meaning, so 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 action ('Issue') and the resource ('new end-entity certificate from a CA'), and the mention of returning private key, certificate, and CA chain distinguishes it from sibling tools like ncloud_pca_sign_end_csr or listing tools.

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?

No guidance is provided on when to use this tool versus alternatives such as ncloud_pca_sign_end_csr or ncloud_issue_private_certificate. There are no contextual hints about prerequisites or exclusions.

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

Deploy Server