Skip to main content
Glama
sagar1012

oracle-sqlplus-mcp

by sagar1012

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SQLPLUS_PATHNoPath to sqlplus binary if not in PATHsqlplus
QUERY_TIMEOUT_MSNoQuery timeout in milliseconds30000
ORACLE_CONNECTIONYesFull Oracle connection string in format username/password@host:port/servicename

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_queryA

Execute a SQL SELECT query against the Oracle database and return the results. Use standard Oracle SQL syntax. Do NOT include a trailing semicolon — it is added automatically.

execute_ddlA

Execute a DDL or DML statement (CREATE, INSERT, UPDATE, DELETE, ALTER, DROP). Use with caution — changes are committed immediately.

list_tablesB

List all tables accessible to the current user, optionally filtered by schema/owner.

describe_tableA

Describe the columns, data types and constraints of a table.

list_schemasA

List all schemas (users/owners) in the database that have at least one table.

get_table_sampleA

Fetch a sample of rows from a table (default: 10 rows).

list_proceduresA

List stored procedures and functions for a given schema.

test_connectionA

Test the Oracle connection and return server version info.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 8 tools

Disambiguation5/5

Every tool has a clearly distinct purpose: describing tables, executing DDL, running queries, sampling rows, listing procedures, schemas, tables, and testing connections. No overlapping functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., describe_table, list_tables), making them easy to parse and predict.

Tool Count5/5

Eight tools is an appropriate number for a database interaction server, covering essential operations without being overwhelming or too sparse.

Completeness4/5

The toolset covers core database operations (querying, DDL/DML, listing objects, describing, sampling) but lacks capabilities like viewing procedure source code or managing users, which are minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues