Raja SQL MCP
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_sqlC | This function helps to execute an sql query |
| list_tablesA | Get all the tables in your Database |
| describe_tableC | This function allows you to get schema of given table name |
| execute_selectC | Execute SELECT Queries and returns rows |
| insert_dataD | Insert Data into the table |
| update_dataD | Update data in the Table |
| delete_dataC | Delete Data from your table |
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 7 tools
Tools are mostly distinct, but execute_select and execute_sql have overlapping functionality since both can run SELECT queries, potentially confusing an agent.
All tools follow a consistent verb_noun pattern (e.g., delete_data, describe_table, execute_sql), with no mixing of conventions.
7 tools is a well-scoped set for a SQL database server, covering essential operations without being excessive or insufficient.
Covers core CRUD and schema inspection, but lacks dedicated tools for table creation or alteration, though execute_sql can handle them.