Skip to main content
Glama
mcp-sql-gateway

mcp-sql-gateway

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GATEWAY_USERYesThe caller's identity. Required.
GATEWAY_DATA_DBNoPath to the data database.data/demo.db
GATEWAY_AUDIT_DBNoPath to the audit log database.data/audit.db
GATEWAY_PROFILESNoPath to the profiles configuration file.config/profiles.yaml

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesA

List the tables and views you are allowed to query.

describe_tableB

Show the columns of a table. Masked columns return hashed values.

run_queryA

Run a single read-only SELECT (SQLite dialect). A row limit is always applied.

my_recent_queriesB

Show your own most recent entries in the audit log.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation5/5

Each tool maps to a distinct step in the query workflow: list_tables (discover), describe_table (inspect schema), run_query (execute), my_recent_queries (audit review). There is no overlap in purpose or return shape, so an agent can select correctly on the first try.

Naming Consistency4/5

All names are lowercase snake_case and three of four follow a verb_noun pattern (describe_table, run_query, list_tables). my_recent_queries is a noun phrase rather than verb-led, a minor deviation but still immediately readable and thematically consistent.

Tool Count5/5

Four tools is well-scoped for a deliberately read-only SQL gateway; each tool covers a necessary phase of the workflow and none feels redundant. Nothing is padded or missing from a minimal viable surface.

Completeness4/5

The read-only lifecycle is fully covered: discovery, schema inspection, execution, and audit traceability, with no dead ends for the stated purpose. Minor gaps exist (no way to inspect indexes/keys or paginate the audit log beyond the default limit), but agents can work around these.