ncloud-gov-mcp-server

ncloud_pca_get_sub_csr

Read-only

Retrieve the Certificate Signing Request (CSR) of an unsigned Sub CA for external signing, enabling certificate issuance for your private CA.

Instructions

Get the CSR (Certificate Signing Request) of a Sub CA for external signing. Only available for unsigned Sub CAs.

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

Input Schema

Name	Required	Description	Default
`caTag`	Yes	CA tag value of the Sub CA

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, which aligns with the description's 'Get' action. The description adds the important behavioral constraint that the tool only works for unsigned Sub CAs, which is useful context beyond the annotation. It does not detail response format, but the annotation covers safety expectations.

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 redundant information. It front-loads the primary action and resource, then adds the essential availability constraint. Every word earns its place.

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?

Given the tool's simplicity (one parameter, read-only annotation, no output schema), the description adequately covers what the tool does and its key constraint. It could mention the output format, but the 'Get' verb implies the CSR is returned. Overall sufficient for effective selection and invocation.

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 only parameter caTag has a description in the schema ('CA tag value of the Sub CA'), providing 100% schema coverage. The tool description does not add additional parameter-level detail, so the baseline 3 is appropriate.

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 (Get), the resource (CSR of a Sub CA), and the purpose (for external signing). The additional constraint 'Only available for unsigned Sub CAs' further clarifies scope and distinguishes it from other PCA get operations like ncloud_pca_get_ca_chain or ncloud_pca_get_ca_crl.

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 for when to use the tool: retrieving a CSR for external signing, and only for unsigned Sub CAs. It does not explicitly name alternative tools, but the 'for external signing' qualifier implicitly connects to the signing workflow, making the usage intent clear.

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

Deploy Server