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

ncloud-gov-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_list_fabric_clusters

Read-only

List all fabric clusters in the current region to view their details and filter results by cluster name or numbers.

Instructions

List all fabric clusters 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_fabric_clusters"
  }
}

Input Schema

NameRequiredDescriptionDefault
fabricClusterNameNoFilter by fabric cluster name
fabricClusterNoListNoFilter by fabric cluster numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the agent knows this is safe read-only. The description adds the 'current region' scoping and 'all' behavior, but doesn't disclose filtering capabilities, pagination, or return format. It adds some value beyond annotations but not rich behavioral context.

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, front-loaded sentence with zero wasted words. It states the operation, target, and scope 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?

This is a simple read-only list operation with no required parameters, no output schema, and strong annotation coverage. The description plus annotations adequately cover the tool's purpose and constraints for an agent to use it effectively. It could mention optional filters, but the schema fills that gap.

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%, with both optional filter parameters (fabricClusterName, fabricClusterNoList) thoroughly described in the schema. The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 applies.

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 uses the specific verb 'List' with resource 'fabric clusters' and scope 'current region', clearly distinguishing it from sibling tools like get_fabric_cluster_detail or pool management tools. It is immediately obvious what the tool does.

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 usage (when you need to list clusters in the current region) but provides no explicit when-to-use guidance, exclusions, or alternatives. Without mentioning when to prefer this over get_fabric_cluster_detail or other cluster tools, usage context is only implied.

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