lolosqltools
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_object_nameB | Validates a SQL object name against BSG Institute naming standards. Returns a list of violations with rule references and suggestions. |
| generate_templateB | Generates a complete, BSG-compliant SQL template for a given object type. Includes all mandatory fields, documentation headers, and constraint naming. |
| get_rulesC | Retrieves BSG SQL standardization rules, optionally filtered by object type and/or topic. |
| validate_sql_objectB | Performs full structural validation of a SQL block (CREATE TABLE, VIEW, SP, FUNCTION, TRIGGER) against BSG standards. Returns a compliance score (0-100) and a list of violations with severity and suggestions. |
| check_audit_fieldsB | Validates that a CREATE TABLE statement includes all mandatory BSG audit fields (Estado, UsuarioCreacion, UsuarioModificacion, FechaCreacion, FechaModificacion, RowVersion) with correct types and a properly named PRIMARY KEY. |
| suggest_aliasA | Generates a BSG-standard table alias from a SQL object name. The alias is built from the first letter of each PascalCase word after stripping the prefix. Detects conflicts with existing aliases and suggests alternatives. |
| format_sqlA | Applies BSG-standard formatting to SQL: uppercases keywords, reformats SELECT columns to leading-comma style, normalizes clause indentation (FROM/WHERE/JOIN), separates AND/OR conditions to their own lines, normalizes BEGIN...END indentation to 4 spaces, and removes inline -- comments from the code body. |
| check_performance_patternsA | Detects SQL anti-patterns and performance bad practices against BSG standards. Returns categorized violations sorted by severity (CRITICAL > HIGH > MEDIUM > LOW). |
| generate_production_requestB | Generates a formatted production deployment request email following BSG's mandatory format. Includes automatic warnings for schedule issues, schema problems, and BSG policy compliance. |
| generate_access_requestB | Generates a formatted database access request email following BSG's mandatory format. Groups objects by type, validates permissions, and checks compliance with BSG access policy. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| BSG General Rules | General SQL standardization rules applicable to all objects |
| BSG Table Rules | Rules for creating and naming SQL tables |
| BSG View Rules | Rules for creating and naming SQL views |
| BSG Stored Procedure Rules | Rules for creating and naming stored procedures |
| BSG Function Rules | Rules for creating and naming SQL functions |
| BSG Trigger Rules | Rules for creating and naming SQL triggers |
| Table Example | Complete example of a BSG-compliant SQL table |
| View Example | Complete example of a BSG-compliant SQL view |
| Stored Procedure Example | Complete example of a BSG-compliant stored procedure |
| Function Example | Complete example of a BSG-compliant SQL function |
| Constraint Naming Rules | All constraint naming conventions (PK, FK, DF, CHK, UQ) |
| Audit Fields Reference | Mandatory audit fields for all tables |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: validation (check_audit_fields, validate_object_name, validate_sql_object), generation (generate_template, suggest_alias, generate_production_request, generate_access_request), retrieval (get_rules), formatting (format_sql), and performance checks (check_performance_patterns). No two tools appear to perform the same action, and their boundaries are well-defined.
All tool names consistently use the verb_noun pattern (e.g., check_audit_fields, get_rules, validate_object_name, generate_template). There is no mixing of conventions like camelCase or inconsistent verb styles.
The server provides 10 tools, which is appropriate for its domain of SQL standardization and validation. Each tool covers a distinct, necessary operation, and none appear redundant or superfluous.
The tool surface covers key operations for SQL standardization: validation, template generation, formatting, rule retrieval, alias suggestion, and request generation. However, there is no explicit tool for updating or deleting SQL objects, and no tool for retrieving all validation results at once, though agents can work around these gaps by combining existing tools.