Skip to main content
Glama
Sign In
OceanBase Oracle MCP Server

OceanBase Oracle MCP Server

by EwanJasper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_table_indexes

Retrieves index information including index name, type, uniqueness, and included columns for a specified Oracle table in OceanBase.

Instructions

获取指定表的索引信息（索引名、类型、唯一性、包含列）。

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_indexes"
  }
}

Input Schema

NameRequiredDescriptionDefault
table_nameYesOracle 表名（大写）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states the action (get indexes) without disclosing read-only nature, performance, prerequisites, or side effects. Minimal behavioral context.

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?

The description is a single sentence that directly states the purpose and key output fields. No unnecessary words, front-loaded and efficient.

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, the description lists the output fields (index name, type, uniqueness, included columns), which is helpful. Could be more explicit about output format, but covers essential information.

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% (table_name with description). The description does not add additional parameter meaning beyond what is in the schema, meeting the baseline for adequate coverage.

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 retrieves index information (name, type, uniqueness, included columns) for a specified table, matching the tool name and distinguishing it from siblings like get_table_schema.

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 but does not explicitly state when to use this tool over alternatives (e.g., get_table_schema). It lacks context about when not to use it.

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