MSSQL 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 |
|---|---|
| queryC | Execute a SQL query on a MSSQL 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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, it inherently has perfect naming consistency with itself. The tool name 'query' follows a simple verb pattern, and there are no other tools to create inconsistency.
A single tool for an MSSQL server is too few for the apparent scope, as it lacks basic operations like listing tables, describing schemas, or executing parameterized queries. This minimal set will likely cause agent failures due to incomplete functionality.
The tool surface is severely incomplete for an MSSQL database server. While the 'query' tool allows executing SQL, there are significant gaps such as no tools for metadata exploration, transaction management, or data manipulation beyond raw queries, which are essential for typical database workflows.