SQL MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tablesC | Get list of table in database |
| get_columnsC | Get list of column in a table |
| execute_queryC | Run a query to database |
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: execute_query runs queries, get_columns lists columns in a table, and get_tables lists tables in a database. There is no overlap or ambiguity between these operations.
All tool names follow a consistent verb_noun pattern (execute_query, get_columns, get_tables) with clear, descriptive verbs and nouns. No deviations or mixed conventions are present.
With only 3 tools, the server feels thin for an SQL domain, lacking operations like insert, update, delete, or schema modifications. While the tools are well-defined, the count is borderline low for comprehensive database interaction.
The tool set is severely incomplete for an SQL server, missing essential CRUD operations (e.g., insert, update, delete) and schema management tools. This will cause significant agent failures when trying to perform common database tasks beyond basic queries and metadata retrieval.