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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_create_placement_group

Create a placement group to control physical server placement, enabling anti-affinity or other placement strategies for your servers.

Instructions

Create a new placement group for physical server placement control

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ncloud_create_placement_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
placementGroupNameNoPlacement group name (max 30 characters)
placementGroupTypeCodeNoPlacement group type code (default: AA - Anti-Affinity)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.5/5.0
Behavior2/5

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

Annotations only include destructiveHint=false, which is consistent with 'Create'. The description adds no context about side effects, idempotency, required permissions, or response format. Since annotations are minimal, the description carries the burden and falls short.

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, front-loaded sentence with no filler. Every word contributes to the meaning, making it highly concise and well-structured.

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

Completeness3/5

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

The tool is relatively simple with only two optional parameters and no output schema. The description and schema are adequate for basic invocation, but the lack of behavioral details and usage guidance leaves some gaps for an agent to fully understand the tool's effects.

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 description coverage is 100%, so the schema fully documents both parameters. The description adds no parameter-specific meaning beyond what is already in the schema, so the baseline score of 3 is appropriate.

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 ('Create'), the resource ('placement group'), and the purpose ('for physical server placement control'). This distinguishes it from sibling tools like list/get/delete placement group, which have different verbs and resources.

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 implies when to use the tool (when you need to create a placement group), but it does not explicitly mention alternatives or exclusions. No guidance is given about prerequisites or when not to use it.

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