SQL-Transpiler MCP Tool
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| DialectsB | List all available SQL dialects supported by sqlglot. |
| TranspilerA | Transpile SQL queries from one dialect to another using sqlglot. First, run the Dialects tool to check if both the source and target dialects are supported. |
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 2 tools
The two tools have perfectly distinct purposes: Dialects lists available SQL dialects, while Transpiler converts queries between dialects. There is no overlap in functionality, and the descriptions clearly differentiate their roles, making misselection impossible.
Both tools use clear, descriptive noun-based names (Dialects and Transpiler) that align with their functions. While not following a strict verb_noun pattern, they are consistently styled and immediately understandable within the server's domain.
With only two tools, the server feels thin for its stated purpose of SQL transpilation. While the tools cover core functionality (listing dialects and transpiling), additional tools for validation, parsing, or error handling could enhance completeness. The count is borderline but workable.
The tools cover the essential workflow of checking dialects and transpiling queries, but there are notable gaps. Missing operations include validating SQL syntax, optimizing queries, or handling errors during transpilation. The surface is functional but minimal, potentially requiring workarounds for advanced use cases.