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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_pca_get_end_cert

Read-only

Fetches details of an end-entity certificate using its serial number and CA tag. Enables inspection of certificate metadata in NCP government cloud.

Instructions

Get detailed information of a specific end-entity certificate by serial number.

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>",
      "serialNo": "<serialNo>"
    },
    "name": "ncloud_pca_get_end_cert"
  }
}

Input Schema

NameRequiredDescriptionDefault
caTagYesCA tag value
serialNoYesCertificate serial number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

The annotation readOnlyHint=true already indicates a safe read operation; the description adds the selection criterion (by serial number) which is consistent. However, no additional context is provided about error cases, response details, or the need to specify a CA tag.

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?

One concise sentence that clearly communicates the tool's function with no unnecessary words.

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 simple read-only getter with two documented parameters and no output schema, the description is adequate but does not mention the required CA context or how to obtain the serial number, leaving some ambiguity for agents.

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 full descriptions for both caTag and serialNo (100% coverage), so the description adds no extra parameter semantics beyond restating 'by serial number.' 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 detailed information'), the specific resource ('specific end-entity certificate'), and the lookup method ('by serial number'). It distinguishes this from the sibling 'ncloud_pca_list_end_certs' which lists certificates.

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 usage when a serial number is known, but it does not explicitly state when to use this tool versus listing certificates first or any alternatives. It lacks exclusions or hints such as 'use list_end_certs to find the serial number first.'

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