oracle-mcp-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| awr_analyzeB | Analyze an Oracle AWR or ASH report (HTML or text, 10g-23ai, incl. RAC global). Returns DB info, load profile, top wait events and top SQL with tuning advice, recommendations and a top-3 tuning_summary. |
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 1 tool
With only a single tool there is no possibility of confusion or misselection. The purpose (analyze AWR/ASH reports) is clearly stated and unambiguous.
The lone name awr_analyze follows a clear noun_verb snake_case pattern, though a single data point makes consistency trivially satisfied rather than demonstrated across a set.
A one-tool surface is too thin for a database diagnostics server; everything hinges on the user already having a report file. Typical tuning workflows (connect, list snapshots, fetch report) have no supporting tools.
The analysis itself appears thorough (DB info, waits, top SQL, recommendations), but the lifecycle is a dead end: there is no tool to retrieve or generate an AWR/ASH report from a database, and no follow-up tools for deeper drill-down.