SqlAugur
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SqlAugur__MaxRows | No | Maximum rows returned per query | 1000 |
| SqlAugur__AzureKeyVaultUri | No | Azure Key Vault URI (e.g., https://myvault.vault.azure.net/). When set, secrets from the vault are added as a configuration source. | |
| SqlAugur__EnableDarlingData | No | Enable DarlingData diagnostic tools (sp_PressureDetector, sp_QuickieStore, etc.) | false |
| SqlAugur__EnableWhoIsActive | No | Enable sp_WhoIsActive session monitoring | false |
| SqlAugur__MaxQueriesPerMinute | No | Maximum queries allowed per minute (token bucket rate limit) | 60 |
| SqlAugur__MaxConcurrentQueries | No | Maximum number of SQL queries that can execute concurrently | 5 |
| SqlAugur__CommandTimeoutSeconds | No | SQL command timeout for all queries and procedures | 30 |
| SqlAugur__EnableDynamicToolsets | No | Enable progressive tool discovery — DBA tools load on demand via 3 meta-tools instead of at startup. | false |
| SqlAugur__EnableFirstResponderKit | No | Enable First Responder Kit diagnostic tools (sp_Blitz, sp_BlitzFirst, etc.) | false |
| SqlAugur__Servers__production__ConnectionString | No | The connection string for a SQL Server instance named 'production'. Format: Server=myserver;Database=master;Integrated Security=True;TrustServerCertificate=False;Encrypt=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 | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_extended_propertiesA | Read extended properties (descriptions, metadata) from tables and columns. Returns JSON with schema, table, column, property name, and value. |
| describe_tableA | Get comprehensive metadata about a single table including columns, data types, indexes, primary key, foreign keys, check constraints, and default constraints. |
| get_plantuml_diagramA | Generate a PlantUML ER diagram saved to a file. Shows tables, columns, PKs, and FK relationships with smart cardinality. |
| list_databasesA | List all databases on a named SQL Server instance. Returns database names, IDs, states, and creation dates. Use list_servers first to discover available server names. |
| get_schema_overviewA | Markdown overview of database schema: tables, columns, types, PKs, FKs, unique/check constraints, defaults. Use get_plantuml_diagram for visual ER output or describe_table for single-table detail. |
| get_object_dependenciesA | Show what a database object references and what references it. Returns JSON with 'references' and 'referencedBy' arrays for dependency analysis. |
| get_mermaid_diagramA | Generate a Mermaid ER diagram saved to a file. Shows tables, columns, PKs, and FK relationships with smart cardinality. |
| list_programmable_objectsA | List stored procedures, functions, views, and triggers in a database. Returns JSON with schema, name, type, and create/modify dates. |
| get_query_planA | Get the estimated or actual XML execution plan for a SELECT query. Estimated plans show the optimizer's plan without executing. Actual plans execute the query and include runtime statistics. Uses the same query validation as read_data (SELECT only). |
| read_dataA | Execute a read-only SQL SELECT query against a named SQL Server instance. Only SELECT and WITH (CTE) queries are allowed. Use list_servers first to discover available server names. |
| list_serversA | List the available SQL Server instances that can be queried. Call this first to discover server names before using read_data. |
| get_object_definitionA | Get the T-SQL source code of a stored procedure, function, view, or trigger. Returns Markdown with the object type and definition. |
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 targets a distinct operation: describing tables, reading data, listing servers/databases, getting definitions/dependencies/diagrams. The only overlap is between get_mermaid_diagram and get_plantuml_diagram, but these are clearly differentiated by output format, so no ambiguity.
Tools use a mix of get_, list_, describe_, and read_ prefixes. While each group is internally consistent, the overall pattern is not uniform. However, the naming is still predictable and readable.
With 12 tools, the server covers all essential database exploration tasks without being bloated. Each tool serves a clear purpose, and the count feels appropriate for the scope.
The tool set covers schema discovery, object details, dependencies, diagrams, query plans, and read-only data access. Missing a dedicated 'list_tables' tool, but get_schema_overview provides table information. Overall very comprehensive for a read-only database exploration tool.