claude-database-tools
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| READONLY | No | If set to true, disables write operations (insert, update, delete, etc.). | true |
| SQL_PORT | No | The port number for the SQL Server (default is 1433). | 1433 |
| SQL_USER | Yes | The username for SQL Server authentication. | |
| SQL_SERVER | Yes | The SQL Server hostname or IP address. | |
| SQL_ENCRYPT | No | Whether to use encryption for the connection (true/false). | false |
| SQL_DATABASE | Yes | The name of the database to connect to. | |
| SQL_PASSWORD | Yes | The password for SQL Server authentication. | |
| SQL_TRUST_SERVER_CERTIFICATE | No | Whether to trust the server certificate (true/false). | true |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesC | Lists tables in an MSSQL Database, or list tables in specific schemas |
| describe_tableA | Describes the complete schema of a specified MSSQL Database table, including columns, types, constraints, indexes, and foreign keys. |
| read_dataA | Executes a SELECT query on an MSSQL Database table. The query must start with SELECT and cannot contain any destructive SQL operations for security reasons. |
| insert_dataA | Inserts data into an MSSQL Database table. Supports both single record insertion and multiple record insertion using standard SQL INSERT with VALUES clause. FORMAT EXAMPLES: Single Record Insert: { "tableName": "Users", "data": { "name": "John Doe", "email": "john@example.com", "age": 30, "isActive": true, "createdDate": "2023-01-15" } } Multiple Records Insert: { "tableName": "Users", "data": [ { "name": "John Doe", "email": "john@example.com", "age": 30, "isActive": true, "createdDate": "2023-01-15" }, { "name": "Jane Smith", "email": "jane@example.com", "age": 25, "isActive": false, "createdDate": "2023-01-16" } ] } GENERATED SQL FORMAT:
|
| update_dataB | Updates data in an MSSQL Database table using a WHERE clause. The WHERE clause must be provided for security. |
| delete_dataA | Executes a physical DELETE operation on table records. WARNING: This database uses soft delete patterns (__deleted flag). Consider using update_data to set __deleted = 1 instead for most use cases. |
| create_tableC | Creates a new table in the MSSQL Database with the specified columns. |
| create_indexC | Creates an index on a specified column or columns in an MSSQL Database table |
| drop_tableC | Drops a table from the MSSQL Database. |
| get_table_ddlB | Generates CREATE TABLE DDL script for an existing table, including columns, constraints, and optionally indexes. |
| get_table_alter_ddlB | Generates ALTER TABLE DDL statements to add columns and constraints from an existing table. |
| execute_stored_procC | Executes a stored procedure with optional parameters. Supports input parameters and returns result sets, output parameters, and return values. |
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 12 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like create_table, describe_table, and drop_table target different table operations, while insert_data, update_data, delete_data, and read_data cover distinct CRUD actions. The descriptions reinforce these boundaries, such as the warning in delete_data about soft deletes versus update_data.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_table, describe_table, and execute_stored_proc. There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.
With 12 tools, this server is well-scoped for MSSQL database operations. The count covers essential tasks like table management, data manipulation, and schema inspection without being overwhelming. Each tool serves a clear purpose, such as get_table_ddl for DDL generation and list_tables for discovery.
The tool set provides comprehensive coverage for core database operations, including table creation, schema description, data CRUD, and stored procedure execution. Minor gaps exist, such as no explicit tools for managing indexes beyond create_index (e.g., drop_index) or handling transactions, but agents can work around these with existing tools like execute_stored_proc.