MCP SQL Agent
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_schemaB | Get the complete database schema with table structures and sample data |
| list_tablesB | List all tables in the database |
| describe_tableB | Get detailed information about a specific table including columns and sample data |
| query_dataB | Execute SQL queries safely. Use get_schema() first to understand the database structure. |
| search_tablesB | Search for tables or columns containing a specific keyword |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| database_context | Provides context about the database schema for the AI assistant |
| example_prompt |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Some tools have overlapping purposes that could cause confusion. 'describe_table' and 'get_schema' both provide table structure information, with 'get_schema' covering the entire database while 'describe_table' focuses on a specific table. 'list_tables' and 'search_tables' also overlap in table discovery functionality, though 'search_tables' adds keyword filtering.
All tool names follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout: describe_table, get_schema, list_tables, query_data, and search_tables all use the same structure and are immediately understandable.
Five tools is a reasonable number for an SQL agent, providing core database interaction capabilities without being overwhelming. The count feels slightly lean but covers essential operations for exploring and querying databases, though additional tools for data manipulation might be expected.
The toolset covers exploration and querying well but lacks data manipulation operations. There are no tools for creating, updating, or deleting tables or records, which are common SQL operations. The surface is complete for read-only database interaction but incomplete for full database management.