GoSQLX
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 |
|---|---|
| analyze_sqlA | Use this when the user wants a complete review of a SQL query. Runs validate, parse, metadata, security, lint, and format concurrently and returns one composite report; hosts that support MCP Apps render it as an interactive report. |
| extract_metadataA | Use this when the user wants the tables, columns, and functions a SQL query references (e.g. for lineage or impact analysis). Returns {tables, columns, functions}. |
| format_sqlA | Use this when the user wants SQL pretty-printed or reformatted: one clause per line, optional upper-case keywords and trailing semicolon. Comments are preserved; unplaceable optimizer hints are refused. Returns {formatted_sql, options}. |
| lint_sqlA | Use this when the user wants SQL style feedback. Applies the same 10 rules as |
| parse_sqlA | Use this when the user wants to know how SQL parses: returns an AST summary with the statement count and the type of each statement, optionally for a specific dialect. GO batch separators are excluded from the count. |
| security_scanA | Use this when the user wants SQL checked for injection patterns: tautologies, UNION attacks, stacked queries, comment bypasses, and more. Returns findings with severity counts. |
| validate_sqlA | Use this when the user wants to know whether a SQL statement is syntactically valid, optionally for a specific dialect. Returns {valid: bool, error?: string, dialect?: string}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| gosqlx_analysis_report | Interactive GoSQLX analysis report: validity, statement types, referenced tables/columns/functions, security findings by severity, lint violations, and the formatted SQL with a copy button. |
TDQS
Scored across 7 tools
Each tool has a distinct primary action: format, parse, validate, lint, security scan, metadata extraction, and a composite analysis report. The main ambiguity is that `analyze_sql` overlaps with all the individual tools by running them concurrently, so an agent may sometimes choose the composite instead of a targeted tool. Descriptions mitigate this by framing `analyze_sql` as a full review, but the boundary is not perfectly sharp.
Six of seven tools follow a clear verb_noun snake_case pattern: format_sql, parse_sql, analyze_sql, extract_metadata, lint_sql, and validate_sql. `security_scan` deviates slightly because it is a noun compound rather than verb_noun, but it remains readable and thematically consistent.
Seven tools is well-scoped for a SQL analysis and formatting server. Each tool corresponds to a meaningful operation, and there are no redundant or trivial entries beyond the intentional composite `analyze_sql`.
The surface covers the full SQL analysis lifecycle: validation, parsing, formatting, linting, security scanning, metadata extraction, and a composite review. There are no obvious dead ends for the stated domain.