Skip to main content
Glama
Sign In
OceanBase Oracle MCP Server

OceanBase Oracle MCP Server

by EwanJasper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

search_tables

Search table and view names in OceanBase Oracle database by keyword, case-insensitive, to find matching schemas quickly.

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": {
      "keyword": "<keyword>"
    },
    "name": "search_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes搜索关键词（不区分大小写）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so the description carries full burden. It states the tool searches and returns results, implying a read operation, but does not explicitly disclose behavioral traits such as case-insensitivity (only in schema), pagination, or safety guarantees.

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, efficient sentence that covers the tool's functionality without any redundant information. Every word is meaningful.

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?

For a simple search tool with one parameter and no output schema, the description adequately states it returns a list of matching results. However, it does not specify what fields the results contain (e.g., just names or full details), which would be helpful given the lack of output schema.

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% for the single parameter. The description does not add any additional meaning beyond what the schema already provides (e.g., case-insensitivity mentioned in schema but not in description). Baseline of 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?

The description clearly specifies a verb 'search' and resource 'table and view names', distinguishing it from siblings like query_db (executes SQL) and list_tables (lists all tables without keyword).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., query_db or list_tables). The description only states what it does, leaving the agent to infer usage context from the tool name and siblings.

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