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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_get_connections

Read-only

Retrieve a paginated list of data catalog connections, using optional keyword search to find connections by name or description.

Instructions

Get connection list in a catalog

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": {
      "catalogId": "<catalogId>"
    },
    "name": "ncloud_datacatalog_get_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
pageSizeNoPage size 1~200 (default: 20)
catalogIdYesCatalog ID
searchValueNoSearch keyword (connection name or description)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. Description adds no further behavioral detail (e.g., no mention of pagination, filtering behavior, or return format). Does not contradict annotations, but adds minimal value beyond the structured field.

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?

Single sentence of 6 words, front-loaded and to the point. No extraneous information. Every word earns its place.

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?

For a list tool with 4 parameters and no output schema, the description is minimal. It does not explain what a connection is, how the list is returned, or any constraints. Annotations cover safety, but overall context feels insufficient for an agent to fully understand the tool's behavior.

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% with clear parameter descriptions. Description does not add additional meaning or context beyond what the schema already provides. Baseline of 3 is appropriate.

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?

Description clearly identifies the action (Get) and resource (connection list) with scope (in a catalog). Distinguishes from sibling ncloud_datacatalog_get_connection which retrieves a single connection. However, it's terse and could be more specific about what a connection represents.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., ncloud_datacatalog_get_connection for individual connections). Does not provide context for when not to use it or mention any prerequisites. Agent must infer usage from the name alone.

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