Skip to main content
Glama

Related Servers

Alternatives to schemagate

  • A
    license
    A
    quality
    B
    maintenance
    Lets an LLM explore a cryptic legacy ERP schema in plain language through a semantic layer (table listing, column descriptions, published dictionary) and run single read-only SELECT queries that return capped results. Enforces safety at the database engine level: only reads are authorized, sensitive columns are masked to NULL, queries are aborted after a few seconds, and every call is written to an append-only audit log.
    3
    MIT

Related Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    Provides a guarded semantic layer for text-to-SQL, offering tools for schema discovery, semantic profiling, and query verification to enable safe and reliable SQL generation on enterprise databases.
    -
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables natural-language queries over data warehouses with catalog-grounded semantics and per-query authorization, returning answers with attached reasoning.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to understand and query your database safely by providing a semantic layer of metadata, with tools to search, explain, validate, and generate safe SQL.
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Lets AI clients ask natural-language questions about a SQL database with production-safe guardrails, schema grounding, and read-only enforcement.
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI systems to securely query databases using structured intents (MDBP) with automatic schema discovery and policy enforcement.
    8
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to query a read-only data surface through typed tools, enforcing caller-specific row access, field masking, and withheld-row disclosure so they can retrieve entitled information without writes or silent data leakage.
    MIT

TDQS

A4.4/5.0

Scored across 8 tools

Disambiguation4/5

Each tool has a distinct role, and the descriptions explicitly steer callers between the overlapping-looking paths (answer vs. select_schema + run_query, semantic_query vs. run_query). The main ambiguity is that answer and semantic_query both involve the server's model, but the guidance on when to prefer each is clear enough.

Naming Consistency4/5

All names use snake_case and are readable, with most following a verb_noun pattern (select_schema, run_query, describe_object, list_objects, refresh_catalog). The standalone nouns 'answer' and 'health' are minor deviations but remain clear.

Tool Count5/5

Eight tools is well within the sweet spot for a read-only schema-gateway server. Discovery, schema selection, description, querying, semantic filtering, catalog refresh, and health each earn a place without redundancy.

Completeness4/5

The read-only lifecycle is well covered: list objects, select relevant schema, describe objects, run queries, optionally semantic-filter, refresh catalog, and check health. Minor gaps might include explicit SQL validation or richer pagination controls, but agents can work around these.

Maintenance

ActivityNo data
ResponsivenessWithin a week