MCPQL
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 |
|---|---|
| mcp_table_analysisC | Comprehensive SQL Server table analysis including structure, columns, keys, indexes, and constraints |
| mcp_sp_structureC | Analyze SQL Server stored procedure structure including parameters, dependencies, and source code |
| mcp_preview_dataC | Get a preview of data from a SQL Server table with optional filters |
| mcp_get_column_statsC | Get comprehensive statistics for a specific column in a table |
| mcp_execute_procedureC | Execute a SQL Server stored procedure with parameters and return results |
| mcp_execute_queryC | Execute a raw SQL query and return the results |
| mcp_quick_data_analysisB | Quick statistical analysis of a table including row count, column distributions, and top values |
| mcp_search_comprehensiveC | Search across database objects by name and definition with configurable criteria |
| mcp_get_dependenciesC | Get dependencies for a database object (tables, views, stored procedures, etc.) |
| mcp_get_sample_valuesC | Get sample values from a specific column in a table |
| mcp_get_security_statusB | Get current security configuration and status for database operations |
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 11 tools
Most tools have distinct purposes, but some overlap exists: mcp_quick_data_analysis and mcp_table_analysis both analyze tables, which could cause confusion. However, mcp_quick_data_analysis focuses on statistical analysis while mcp_table_analysis covers structure, so descriptions help differentiate them. Other tools like mcp_execute_procedure and mcp_execute_query are clearly distinct.
All tools follow a consistent mcp_verb_noun naming pattern with snake_case throughout. The verbs are descriptive (e.g., execute, get, preview, search, analyze), and the nouns clearly indicate the target (e.g., procedure, query, column_stats, dependencies). This uniformity makes the tool set predictable and easy to navigate.
With 11 tools, the count is well-scoped for a SQL Server database management server. Each tool serves a specific function, from executing queries and procedures to analyzing data and structures, without feeling bloated or sparse. This number allows comprehensive coverage of common database tasks without overwhelming users.
The tool set covers a wide range of SQL Server operations, including query execution, data analysis, structure inspection, and security checks. Minor gaps exist, such as lacking tools for database creation, backup, or user management, but these are not core to the analysis and execution focus. Agents can handle most database interaction workflows effectively with this surface.