MCP DB Wizard
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| select_from_dualA | Returns a single row with one column, DUMMY. This server has NO DATABASE CONNECTION: the value is a fixed message saying so, not a query result, and no SQL is executed. The tool exists to prove that an MCP client can reach this server before Oracle is configured. |
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
Only one tool exists, so there is no possibility of confusing it with another. The description clearly states its purpose as a connectivity check.
With a single tool, the naming pattern is trivially consistent. The name 'select_from_dual' follows a verb_preposition_noun convention, though it may mislead about actual behavior.
The server is named 'MCP DB Wizard' but exposes only one trivial tool that does not perform any database operation. This is an extreme mismatch between scope and count.
The tool only returns a fixed message and executes no SQL. For a server implying database wizardry, the surface is severely incomplete, covering only a placeholder health check.