ncloud-gov-mcp-server

ncloud_list_placement_groups

Read-only

Retrieve a list of placement groups in the current region, with optional filters by name or group number.

Instructions

List all placement groups in the current region

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_list_placement_groups"
  }
}

Input Schema

Name	Required	Description	Default
`placementGroupName`	No	Filter by placement group name
`placementGroupNoList`	No	Filter by placement group numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The readOnlyHint annotation already signals a safe read operation, and the description adds the region-scoping behavior. It does not mention pagination, response contents, or filtering semantics beyond 'all,' but for a read-only listing this is acceptable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that is easy to scan and free of fluff. It loses a point for not including any usage hints or caveats, but it remains appropriately concise.

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 list tool with fully documented optional filters and a readOnlyHint annotation, the description covers the core behavior sufficiently. No output schema exists, but the tool is low-complexity and the description is adequate for selection and invocation.

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?

Both parameters are fully described in the schema with 100% coverage, so the description adds no extra semantic value beyond naming the filters. Baseline 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 states a specific verb ('List'), a clear resource ('placement groups'), and scope ('current region'), making it easy to distinguish from sibling tools like get_placement_group_detail or create_placement_group.

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 use for retrieving placement groups but provides no explicit guidance on when to choose this over get_placement_group_detail or how the optional filters should be applied. It relies on the tool name and schema to convey the listing role.

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

Deploy Server