Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
READONLYNoRestrict to read-only operationsfalse
SQL_USERNoUsername (local SQL Server only)
SERVER_NAMENoSQL Server hostname
SQL_PASSWORDNoPassword (local SQL Server only)
DATABASE_NAMENoTarget database name
TRUST_SERVER_CERTIFICATENoTrust self-signed certificatesfalse

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

NameDescription
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:

  • Single: INSERT INTO table (col1, col2) VALUES (@param1, @param2)

  • Multiple: INSERT INTO table (col1, col2) VALUES (@param1, @param2), (@param3, @param4), ... IMPORTANT RULES:

  • For single record: Use a single object for the 'data' field

  • For multiple records: Use an array of objects for the 'data' field

  • All objects in array must have identical column names

  • Column names must match the actual database table columns exactly

  • Values should match the expected data types (string, number, boolean, date)

  • Use proper date format for date columns (YYYY-MM-DD or ISO format)

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.

describe_tableA

Describes the schema (columns and types) of a specified MSSQL Database table.

update_dataB

Updates data in an MSSQL Database table using a WHERE clause. The WHERE clause must be provided for security.

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.

list_tableC

Lists tables in an MSSQL Database, or list tables in specific schemas

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: create_index (index creation), create_table (table creation), describe_table (schema inspection), drop_table (table deletion), insert_data (data insertion), list_table (table listing), read_data (data querying), and update_data (data modification). The tools cover different aspects of database operations without overlap.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_table, describe_table, drop_table, insert_data, list_table, read_data, update_data). The naming is uniform and predictable, making it easy for agents to understand the action and target resource.

Tool Count5/5

With 8 tools, this server is well-scoped for MSSQL database operations. Each tool serves a specific and necessary function in the domain, such as table management, data manipulation, and schema inspection, without being overly sparse or bloated.

Completeness4/5

The tool set provides strong coverage for core database operations, including table lifecycle (create, describe, list, drop), data CRUD (insert, read, update), and index creation. A minor gap exists with no explicit tool for deleting data (e.g., delete_data) or managing indexes beyond creation, but agents can work around this using update_data or other methods.