sql-explorer
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 |
|---|---|
| pingA | Check that the server is alive. |
| list_tablesA | List the names of every table in the database. |
| describe_tableA | Describe the columns of one table: name, type, and whether it is required. |
| run_queryA | Run a read-only SELECT query and return the rows. At most 500 rows come back; if the query matched more, "truncated" is true and you should add a LIMIT or aggregate instead. Queries running longer than 5 seconds are aborted. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze_table | Explore one table properly: size, distributions, gaps and outliers. |
| data_quality_report | Hunt for broken or suspicious data across the whole database. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_overview | Every table in the database, with its columns, as one readable page. |
TDQS
Scored across 4 tools
Each tool serves a unique purpose: health check, table enumeration, schema inspection, and query execution. No two tools overlap in functionality, making misselection nearly impossible.
All tool names follow a consistent verb_noun pattern (ping, list_tables, describe_table, run_query), using lowercase with underscores throughout. The naming clearly indicates the action and target.
With only 4 tools, the server is tightly scoped for its read-only SQL exploration purpose. Each tool is essential and covers the core workflow without unnecessary bloat.
The tool set covers the full exploration lifecycle: check health, list tables, describe schema, and run queries. Minor gaps like database-level metadata or caching are not needed for the stated purpose, so it is nearly complete.