ncloud-gov-mcp-server

ncloud_sourcebuild_list_runtimes

Read-only

List available runtime types for a specific OS in SourceBuild, enabling you to choose a compatible runtime.

Instructions

List available runtime types for a specific OS in SourceBuild

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": {
      "osId": "<osId>"
    },
    "name": "ncloud_sourcebuild_list_runtimes"
  }
}

Input Schema

Name	Required	Description	Default
`osId`	Yes	OS ID (from list_os)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The readOnlyHint annotation already indicates a safe read operation, and the description does not contradict it. The description adds minimal behavioral context beyond the annotation, such as the fact that it is OS-scoped, but does not disclose output format or other behaviors. Given the annotation coverage, this meets the baseline.

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 concise sentence that is front-loaded with the verb and object. Every word earns its place, with no redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one parameter, readOnlyHint annotation, and no output schema, the description is complete enough. It specifies what is listed and the scoping requirement (OS), and the return value is implied by the action of listing runtime types.

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 with a description for osId that references list_os. The tool description itself adds no additional meaning beyond the schema, so the schema handles the parameter semantics. The cross-reference in the schema is helpful but not attributable to the description.

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 tool lists available runtime types for a specific OS in SourceBuild, with a specific verb and resource. It distinguishes from the sibling tool list_runtime_versions by focusing on types rather than versions, even though this distinction is not explicitly stated.

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 and schema parameter hint that osId should come from list_os ('OS ID (from list_os)'), which implies a prerequisite. However, there is no explicit guidance on when to use this tool versus alternatives like list_runtime_versions or list_compute, and no exclusions are mentioned.

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

Deploy Server