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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_get_placement_group_detail

Read-only

Query a placement group by its number to retrieve detailed configuration and resource information for infrastructure management.

Instructions

Get detailed information about a specific placement 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": {
      "placementGroupNo": "<placementGroupNo>"
    },
    "name": "ncloud_get_placement_group_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
placementGroupNoYesPlacement group number to query

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint annotation already indicates this is a safe read operation. The description adds minimal behavioral context beyond what the annotation and name convey, such as what 'detailed information' includes or any error/precondition behavior. There is no contradiction with annotations.

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 clear sentence with no filler or redundant information. It front-loads the action ('Get') and resource ('specific placement group') efficiently.

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 get-by-ID tool with one parameter and no output schema, the description provides sufficient context to understand its purpose. However, it does not enumerate what details are returned or mention any prerequisites beyond the parameter, leaving some ambiguity for an agent expecting richer output.

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% and the sole parameter placementGroupNo is described as 'Placement group number to query'. The tool description does not add extra semantics about the parameter's origin or format, so it is adequate but not enhanced.

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 verb 'Get' and the resource 'specific placement group', distinguishing it from sibling tools like ncloud_list_placement_groups. It precisely indicates this is a detail lookup for one placement group, not a list or mutation operation.

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 word 'specific' implies the caller needs a placementGroupNo and that this is for a single entity, but there is no explicit guidance on when to use this versus list_placement_groups or other placement group tools. No alternatives or 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

Other Tools