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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_get_tables_by_database

Read-only

Retrieve tables within a specific database by providing catalog ID and database name. Supports pagination to control result size.

Instructions

Get table list in a specific database

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>",
      "databaseName": "<databaseName>"
    },
    "name": "ncloud_datacatalog_get_tables_by_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
pageSizeNoPage size 1~200 (default: 20)
catalogIdYesCatalog ID
databaseNameYesDatabase name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.10.1

TDQS

C2.9/5.0
Behavior2/5

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

The description only states 'Get table list', which is consistent with the readOnlyHint annotation. However, it provides no additional behavioral details such as pagination behavior (already in schema) or any side effects. Since annotations already declare read-only, the description adds minimal transparency beyond the structured fields.

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?

The description is a single concise sentence with no redundant words. It is front-loaded with the action and resource. However, it is too brief to cover all necessary context.

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?

There is no output schema, so the description should hint at the return format (e.g., list of table objects). It does not. The tool is simple but lacks completeness regarding what the response contains. Sibling tools like 'ncloud_datacatalog_get_table' suggest table details, but this is not clarified.

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 covers all 4 parameters with descriptions (100% coverage), so baseline is 3. The description does not add any extra meaning or context about the parameters; it relies entirely on the schema. No credit for repeating schema info.

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 states it retrieves a list of tables within a specific database, matching the tool name. However, it does not specify what information is included in the table list (e.g., names, metadata), and could better distinguish from sibling tools like 'ncloud_datacatalog_get_tables' which might not require a database scope.

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 guidance on when to use this tool versus similar siblings such as 'ncloud_datacatalog_get_tables' or 'ncloud_datacatalog_get_table'. There is no mention of prerequisites, context, or when not to use this tool.

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