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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_pca_sign_sub_csr

Read-only

Sign a subordinate CA CSR with a parent CA to issue an intermediate CA certificate. Specify the CA tag, CSR in PEM, and validity period.

Instructions

Sign a Sub CA CSR using this CA to issue an intermediate CA certificate.

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>",
      "period": "<period>",
      "csrPem": "<csrPem>"
    },
    "name": "ncloud_pca_sign_sub_csr"
  }
}

Input Schema

NameRequiredDescriptionDefault
caTagYesCA tag value of the signing (parent) CA
csrPemYesCSR in PEM format
periodYesValidity period in days (1-3650)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.2/5.0
Behavior1/5

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

The description says 'Sign a Sub CA CSR' which is a mutating operation (creating an intermediate CA certificate), but the annotations declare readOnlyHint: true. This is a direct contradiction. The description does not disclose any side effects, permissions, or lifecycle implications beyond what the annotation incorrectly claims.

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 with no filler. It front-loads the action and purpose, making it easy to parse.

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

Completeness2/5

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

Given the annotation contradiction and lack of output schema, the description fails to provide necessary behavioral context. It does not mention that this operation is irreversible, requires CA private key access, or that it creates a new certificate. The one-line description is insufficient for a PKI mutation tool.

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%, so the schema already explains all three parameters (caTag, csrPem, period) adequately. The description adds minimal extra meaning—it implies the CSR is for a Sub CA and the CA signs it, but does not clarify parameter format or interactions beyond schema.

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 uses a specific verb ('Sign') and a specific resource ('Sub CA CSR'), and clearly states the outcome ('to issue an intermediate CA certificate'). It distinguishes itself from sibling tools like ncloud_pca_sign_end_csr by explicitly targeting Sub CA CSRs rather than end-entity CSRs.

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 the use case (when you need to issue an intermediate CA certificate from a Sub CA CSR) but does not explicitly state when to use this tool versus alternatives, such as ncloud_pca_sign_end_csr or ncloud_pca_issue_end_cert. No exclusions or prerequisites are mentioned.

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