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

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_datacatalog_get_table_schema_by_version

Read-only

Retrieve the schema for a specific table version in Naver Cloud Data Catalog. Use the version ID from getTableSchemaVersions to view column definitions and metadata.

Instructions

Get table schema for a specific version

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>",
      "tableName": "<tableName>",
      "versionId": "<versionId>"
    },
    "name": "ncloud_datacatalog_get_table_schema_by_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoNoPage number (default: 1)
pageSizeNoPage size 1~200 (default: 20)
catalogIdYesCatalog ID
tableNameYesTable name
versionIdYesSchema version ID (from getTableSchemaVersions)
databaseNameYesDatabase 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 is consistent with the description. However, the description adds no additional behavioral insights beyond the schema's read-only nature. It does not mention potential pagination (given pageNo and pageSize parameters) or error conditions. With annotations covering the safety profile, the description is adequate but minimal.

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 extremely concise at 7 words. It is front-loaded and to the point. However, it could include a bit more context (e.g., 'for the given catalogId, databaseName, tableName, and versionId') without becoming verbose. A single sentence is acceptable.

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?

The description lacks important context. It does not explain that versionId is obtained from a prior call (getTableSchemaVersions), nor does it indicate pagination behavior despite pageNo and pageSize parameters. With no output schema, the agent has no information about what the returned schema looks like. This is insufficient for a tool with 6 parameters.

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?

All 6 parameters are fully described in the input schema (100% coverage). The description adds no extra meaning beyond the parameter descriptions. Baseline 3 is appropriate since the schema already documents parameter purposes.

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 clearly states it gets a table schema for a specific version. This distinguishes it from sibling tools like ncloud_datacatalog_get_table_schema (which likely gets the latest) and ncloud_datacatalog_get_table_schema_versions (which lists versions). The verb 'Get' and resource 'table schema for a specific version' are precise.

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 is provided on when to use this tool versus alternatives. It does not mention that versionId should come from getTableSchemaVersions, nor does it exclude use cases. The agent is left without context on prerequisites or when to prefer this over the non-versioned schema retrieval.

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