Skip to main content
Glama
Sign In
OceanBase Oracle MCP Server

OceanBase Oracle MCP Server

by EwanJasper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_table_schema

Get column details (name, data type, length, nullable) for a table in OceanBase Oracle mode. Input the uppercase table name.

Instructions

获取指定表的列信息（列名、数据类型、长度、是否可空）。table_name 为大写表名。

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": {
      "table_name": "<table_name>"
    },
    "name": "get_table_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_nameYesOracle 表名（大写）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided, so the description bears the full burden. It discloses that table_name must be uppercase and that output includes column attributes, but omits read-only nature, error behavior for missing tables, performance implications, or any side effects.

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?

Two short sentences, no redundant information. Efficiently conveys purpose and key constraint. However, could be slightly more structured with a separate sentence for usage conditions.

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?

Given no output schema and only one parameter, the description adequately explains what the tool returns (column details) and input requirement (uppercase table name). It lacks mention of ordering or filtering, which is acceptable for a simple schema retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value beyond the schema by specifying that table_name must be uppercase and for Oracle, and that the output includes specific column attributes. This clarifies input semantics and expected result.

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 a specific verb 'get' and resource 'table schema', listing the exact output columns (column name, data type, length, nullable). This clearly distinguishes it from sibling tools like list_tables (which lists table names) or get_table_indexes.

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 column details for a known table, but does not explicitly state when to use it over alternatives like query_db or search_tables. It mentions table_name must be uppercase, but no exclusion criteria or prerequisites.

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