ask-oracle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORACLE_USER | Yes | Oracle database username | |
| ORACLE_SERVER | Yes | Oracle database connection string in the format host:port/service_name | |
| ORACLE_PASSWORD | Yes | Oracle database password |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | Lists table names for the connected schema or an explicit OWNER, optionally filtered by a SQL LIKE pattern. Call this before describe_table; it does not return columns. |
| describe_tableA | Returns column names, data types, and nullability for exactly one table. Call this only for tables relevant to the question. |
| run_sqlA | Executes read-only SELECT/WITH SQL. This server was not started with --allow-write, so DML/DDL is disabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing tables, describing a table's schema, and executing read-only SQL. There is no overlap between these operations, so an agent can confidently select the right tool.
All tool names follow a consistent verb_noun snake_case pattern: list_tables, describe_table, run_sql. The naming is predictable and matches the tool's action and target.
Three tools is an appropriate scope for a read-only database exploration server. Each tool covers a necessary step in the workflow without unnecessary bloat.
The tool set fully covers the domain of read-only Oracle database exploration: discover tables, inspect schemas, and run queries. No obvious missing operations are needed for the stated purpose.