Skip to main content
Glama
Oracle Schema Explorer MCP Server

Oracle Schema Explorer MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ORACLE_CONNECTION_STRINGNoOracle connection string. Can be left empty and set dynamically in chat via the set_connection tool. Supported formats include EzConnect, URL syntax, or TNS descriptor.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
set_connectionB

Sets or switches the active Oracle database connection string dynamically.

Args: connection_string: Oracle connection string (e.g. 'user/password@host:1521/service_name').

get_connection_infoA

Checks current database connection status, Oracle version, and session details.

list_schemasA

Lists accessible schemas in the Oracle database with table counts.

list_tablesB

Lists tables and views in a specified schema with row counts.

Args: schema: Name of schema/owner (defaults to current user).

describe_tableA

Retrieves full column metadata for a table: data types, lengths, nullability, PK status.

Args: table_name: Name of the table. schema: Optional schema/owner name.

get_table_connectionsC

Explores how a table is connected to other tables (Outgoing and Incoming Foreign Keys).

Args: table_name: Table name. schema: Optional schema/owner name.

get_schema_relationshipsB

Generates the complete Entity-Relationship diagram for tables in a schema.

execute_readonly_queryA

Executes a strictly READ-ONLY query (SELECT/WITH) with automatic ROWNUM capping.

Args: sql_query: A SELECT or WITH query to execute. max_rows: Maximum number of rows to return (1-500, default 50).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct resource and action: connection management, schema listing, table listing, column metadata, table-level foreign keys, schema-wide ER relationships, and read-only queries. The closest pair, get_table_connections and get_schema_relationships, is clearly differentiated by table-level vs schema-wide scope.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: set_connection, get_connection_info, list_schemas, list_tables, describe_table, get_table_connections, get_schema_relationships, execute_readonly_query. Verb choices are varied but conventional and predictable.

Tool Count5/5

Eight tools is well-scoped for a schema exploration server, with no redundant or filler operations. Each tool covers a meaningful step in the exploration workflow.

Completeness4/5

The surface covers connection setup/status, schema and table discovery, column metadata, foreign-key relationships, ER diagrams, and ad-hoc read-only querying, which supports core exploration workflows. Minor gaps include object search/filtering and index or non-PK constraint inspection, though these can be partially worked around via execute_readonly_query.

Maintenance

ActivityMaintained
ResponsivenessSyncing