Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_server_detail

Read-only

Retrieve a single server instance's details, including attached block storages and tags, to get complete resource context in one call.

Instructions

Get one server instance plus what is attached to it: block storages (boot + additional, with size/type/product code) and tags. The Server API's detail payload is field-for-field identical to the list entry, so the extra context is what makes this tool worth calling over ncloud_list_servers. Billing type / contract are NOT in the Server API — price a server with ncloud_get_product_price_list (billing group) using serverProductCode or serverSpecCode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeRelatedNoAlso fetch attached block storages and tags (two extra read calls). false = bare getServerInstanceDetail payload.
serverInstanceNoYesServer instance number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / includeRelated
      Added value: +{
+  "default": true,
+  "description": "Also fetch attached block storages and tags (two extra read calls). false = bare getServerInstanceDetail payload.",
+  "type": "boolean"
+}
  2. First observedv1.10.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral context: includeRelated triggers two extra read calls and false returns the bare payload. It also clarifies that the detail payload is identical to the list entry, preventing agents from expecting richer server data from this call.

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?

Three dense sentences carry the core action, the differentiation from the main sibling, and the pricing alternative without fluff. The key value proposition is front-loaded, and every sentence earns its place.

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 read tool with no output schema, the description covers what is returned, what extra data includeRelated fetches, the cost of doing so, and what is deliberately not available. An agent has enough context to call it correctly and avoid misuse.

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?

Schema coverage is 100% and both parameters have descriptions. The description adds extra meaning by specifying what 'related' includes: boot and additional block storages with size/type/product code, plus tags. This goes slightly beyond the schema's generic mention of block storages and tags.

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 opens with a specific verb-resource pair ('Get one server instance') and clearly enumerates what is included beyond the basic instance: block storages and tags. It explicitly contrasts this tool with ncloud_list_servers, so an agent can distinguish them at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent when to prefer this tool over ncloud_list_servers ('extra context is what makes this tool worth calling'). It also excludes pricing/contract concerns and routes to ncloud_get_product_price_list, giving a clear alternative for a different need.

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