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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ses_get_versions

Read-only

Fetch the list of available search engine versions, including Elasticsearch and OpenSearch, for configuration and deployment.

Instructions

Get available Search Engine (Elasticsearch/OpenSearch) versions

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_ses_get_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The readOnlyHint annotation aligns with the 'Get' action, so there is no contradiction. However, the description adds no extra behavioral context, such as the format of the returned versions or any regional considerations. Given the annotation, this is acceptable but minimal.

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, compact sentence of ten words, with the action and object front-loaded. Every word is necessary; there's no fluff or repetition.

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 zero-parameter read-only operation, the description sufficiently communicates the tool's output scope. It lacks details on the response format, but the absence of an output schema and the simple nature of the task make this a minor omission. The description is complete enough to inform an agent of the tool's function.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

This tool accepts no parameters, and the input schema is empty. The description doesn't need to explain parameter semantics, so the baseline score of 4 applies. It does specify the engine type (Elasticsearch/OpenSearch), which provides context beyond an empty 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 ('Get') and resource ('available Search Engine versions'), explicitly naming Elasticsearch/OpenSearch. This clearly differentiates it from sibling version tools like ncloud_nks_get_versions (Kubernetes) and ncloud_cdss_get_kafka_versions (Kafka).

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 offers no explicit guidance on when to employ this tool versus similar version-listing siblings. Usage is implied by the name and description, but no alternatives or exclusions are mentioned, which is a notable gap.

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