ncloud-mcp-server

ncloud_ses_get_node_spec_detail

Read-only

Retrieve server specifications for each node in a Search Engine Service cluster using a cluster instance number. Get detailed hardware info for cluster nodes.

Instructions

Get server specifications for each node in a Search Engine Service cluster

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": {
      "serviceGroupInstanceNo": "<serviceGroupInstanceNo>"
    },
    "name": "ncloud_ses_get_node_spec_detail"
  }
}

Input Schema

Name	Required	Description	Default
`serviceGroupInstanceNo`	Yes	Cluster instance number

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds the scope that it applies to each node in a cluster, but it does not disclose details about the response format, potential errors, or whether pagination or filtering is involved. This is acceptable given the annotation, but not rich.

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, clear sentence that conveys the essential purpose without any fluff. It is well-structured and front-loaded with the verb 'Get'.

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 tool with one parameter and no output schema, the description is reasonably complete. It clearly states what is returned (server specifications) and the context (each node in a cluster). A more detailed enumeration of the specifications or potential limitations would improve completeness, but the current level suffices.

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 has 100% coverage: serviceGroupInstanceNo is described as 'Cluster instance number'. The description adds no additional meaning beyond this, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('server specifications for each node in a Search Engine Service cluster'), making the purpose specific and understandable. It does not explicitly differentiate from sibling tools like ncloud_ses_get_server_specs or ncloud_ses_get_node_list, but the phrase 'for each node' adds useful scope.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or relationship to sibling tools such as ncloud_ses_get_cluster_detail or ncloud_ses_get_node_list.

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

Deploy Server