ncloud-mcp-server

ncloud_get_launch_config_detail

Read-only

Retrieve detailed settings of a specific Auto Scaling launch configuration using its ID to verify or troubleshoot your Naver Cloud infrastructure.

Instructions

Get detailed information about a specific launch configuration for Auto Scaling

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": {
      "launchConfigurationNo": "<launchConfigurationNo>"
    },
    "name": "ncloud_get_launch_config_detail"
  }
}

Input Schema

Name	Required	Description	Default
`launchConfigurationNo`	Yes	Launch configuration number to query

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.10.1Jul 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations provide readOnlyHint=true, and the description ('Get detailed information') is consistent with a read operation. It adds context that the tool is for Auto Scaling but does not disclose return value details or any potential error/fulfillment behavior, though the read-only nature reduces the need for extensive disclosure.

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?

A single, concise sentence that front-loads the action and resource. No filler or redundant phrasing; every word contributes to understanding.

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 mostly complete. However, 'detailed information' is vague and could specify what attributes are returned (e.g., image, instance type, user data), but this does not severely hinder use.

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 fully describes the only parameter (launchConfigurationNo as 'Launch configuration number to query'), giving 100% schema description coverage. The description does not add additional meaning beyond the schema, meeting the baseline for full coverage.

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 ('detailed information about a specific launch configuration'), clearly scoped to Auto Scaling. This distinguishes it from sibling tools like list_launch_configs (listing) and create/delete_launch_config.

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 clearly implies usage when a specific launchConfigurationNo is known, but it does not explicitly mention alternatives or when not to use this tool. No reference to sibling list/delete/create tools is provided, leaving usage guidance mostly implicit.

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

Deploy Server