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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_get_databases

Read-only

Retrieve databases in a data catalog using catalog ID. Filter by name and control page size to find specific databases.

Instructions

Get database 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_databases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
pageSizeNoPage size 1~200 (default: 20)
catalogIdYesCatalog ID (from getCatalogs)
searchValueNoSearch keyword (database name)

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 declare readOnlyHint=true, which covers the safety profile. The description adds no further behavioral detail beyond the basic retrieval action. It does not describe pagination, search behavior, or return structure. Acceptable but not additive.

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?

Single sentence of 5 words is extremely concise. While it conveys the core purpose, it could include a bit more context without becoming verbose. For a simple listing tool, this is nearly optimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not explain what the returned data contains (e.g., list of database names, metadata). This lack of completeness could leave an agent unsure about the return format.

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%; all parameters have descriptions. The tool description does not add any meaning beyond what the schema already provides. 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?

Description uses a specific verb 'Get' and resource 'database list', clearly indicating it retrieves multiple databases within a catalog. It distinguishes from sibling tools like ncloud_datacatalog_get_database (singular) and ncloud_datacatalog_get_tables.

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 offers no guidance on when to use this tool versus alternatives (e.g., getCatalogs first to obtain catalogId, or getDatabases vs getTables). No context is provided about prerequisites or typical usage patterns.

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