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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_add_target

Add server instances to a target group to route traffic and enable load balancing.

Instructions

Add targets (server instances) to a target group

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": {
      "targetGroupNo": "<targetGroupNo>",
      "targetNoList": "<targetNoList>"
    },
    "name": "ncloud_add_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNoListYesList of target (server instance) numbers to add
targetGroupNoYesTarget group number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations provide destructiveHint=false, so the safety profile is covered. The description adds minor context by clarifying targets are server instances but does not disclose other behavioral traits like idempotency, failure conditions, or whether existing targets are affected.

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 communicates the essential purpose with no redundant wording.

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 mutation with two fully described parameters, no output schema, and annotations covering destructive behavior, the description is sufficient for basic use. It lacks mention of prerequisites (target group existence) or duplicate handling, but these are not critical given the tool's simplicity.

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?

Schema coverage is 100% with both parameters described (targetNoList and targetGroupNo). The description merely restates these concepts ('targets', 'target group') without adding format, relationships, or constraints beyond the 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 clearly states the action (Add) and the resource (target group), specifying that targets are server instances. This distinguishes it from siblings like ncloud_remove_target (removes) and ncloud_set_targets (likely replaces all targets).

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?

No explicit guidance on when to use this tool versus alternatives such as ncloud_set_targets or ncloud_remove_target. The context is implied but not stated, leaving the agent to infer when additive behavior is appropriate.

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