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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_pca_get_ca

Read-only

Retrieve detailed information about a Private CA using its tag value. Specify the CA tag to get specific certificate authority details.

Instructions

Get detailed information of a specific Private CA by its tag value.

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

Input Schema

NameRequiredDescriptionDefault
caTagYesCA tag value (identifier)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already communicates safe read-only behavior, and the description is consistent with it ('Get' rather than modify). No additional behavioral details are disclosed—such as what happens for a non-existent tag or what 'detailed information' includes—so the description adds little beyond the annotation.

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 13-word sentence that states the essential action and identifier method with no filler or redundancy.

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 read-only lookup with one required parameter and no output schema, the description is adequate for selection and invocation. However, 'detailed information' is vague and does not clarify the response structure or edge cases, so completeness is good but not maximal.

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 coverage is 100%, with caTag documented as 'CA tag value (identifier)'. The description's phrase 'by its tag value' merely restates the parameter's purpose and adds no new meaning or format constraints. Baseline of 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 uses a specific verb+resource ('Get detailed information of a specific Private CA') and clearly indicates the lookup key ('by its tag value'). This distinguishes it from sibling tools like ncloud_pca_list_cas (list all) and ncloud_pca_get_ca_chain (get chain). The purpose is unmistakable.

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 explicit usage guidance is given. The description does not mention when to prefer this tool over alternatives or note any prerequisites, exclusions, or fallback tools. The sibling context implies a get-vs-list distinction, but the description itself provides no such guidance.

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