ncloud-gov-mcp-server

ncloud_get_fabric_cluster_pools

Read-only

List available fabric cluster pools (physical resource pools) for NCP Government Cloud, with optional filter by pool numbers.

Instructions

List available fabric cluster pools (physical resource pools)

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

Input Schema

Name	Required	Description	Default
`fabricClusterPoolNoList`	No	Filter by fabric cluster pool numbers

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint annotation already declares this as a safe read operation, so the description does not need to repeat that. The description adds a small clarification ('physical resource pools') but provides no details on pagination, response format, or filtering behavior beyond what the schema already contains.

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 concise sentence that immediately states the action and resource. It contains no filler or redundancy, earning the highest score for efficiency.

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?

This is a simple list operation with a readOnly annotation and a single, well-documented optional parameter. The description and schema together are sufficient for the agent to select and invoke the tool correctly, though the absence of an output schema means the agent must infer the return type from the phrase 'List available...'.

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?

The input schema has 100% coverage: the sole parameter fabricClusterPoolNoList is described as 'Filter by fabric cluster pool numbers'. The tool description adds no extra meaning beyond the schema, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List available fabric cluster pools (physical resource pools)' uses a specific verb (List) and identifies the exact resource (fabric cluster pools), making the tool's purpose clear. It distinguishes the resource type from sibling tools like ncloud_list_fabric_clusters, though it does not explicitly name alternatives.

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?

The description provides no guidance on when to use this tool versus related tools such as ncloud_get_fabric_cluster_detail or ncloud_list_fabric_clusters. It does not state any context, prerequisites, or exclusions, leaving the agent to infer usage solely from the tool name.

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

Deploy Server