Skip to main content
Glama
ai-ready-warehouse

ai-ready-warehouse

by KNMDeep

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MAX_ROWSNoMaximum number of rows returned by a query. Defaults to `5000`.5000
AI_SCHEMANoSchema containing the curated AI-ready tables. Defaults to `ai_ready`.ai_ready
WAREHOUSENoSelects the warehouse adapter: `sqlite` (default demo data), `redshift`, or `postgres`.sqlite
AWS_REGIONNoAWS region for Redshift.
DATABASE_URLNoPostgres connection URL. The Postgres adapter also accepts the standard `PG*` variables as an alternative.
REDSHIFT_CLUSTERNoRedshift provisioned cluster identifier, used with `REDSHIFT_DB_USER`.
REDSHIFT_DB_USERNoRedshift database user for a provisioned cluster.
REDSHIFT_DATABASENoRedshift database name.
REDSHIFT_WORKGROUPNoRedshift Serverless workgroup name, used instead of `REDSHIFT_CLUSTER` and `REDSHIFT_DB_USER`.

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
describe_tableA

Columns, types and business descriptions for one ai_ready table. Read the descriptions before writing SQL against the table.

list_tablesA

List the tables in the ai_ready schema: curated, documented, production models. Returns each table with its description. Optional name filter.

queryA

Run one read-only SELECT or WITH query. Prefix every table with ai_ready. (for example ai_ready.customers). Results are capped at 5000 rows, so aggregate or add LIMIT on large tables.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

The three tools form a clean discovery-then-execute pipeline: list_tables finds tables, describe_table inspects a single table's columns, and query executes SQL. Each has a distinct scope with no functional overlap, so an agent can select unambiguously.

Naming Consistency4/5

list_tables and describe_table follow a consistent verb_noun snake_case pattern, and query fits the short imperative style of the set. The only minor deviation is that query is a bare verb rather than verb_noun, but it is still predictable and readable.

Tool Count4/5

Three tools is on the lean side but well matched to a read-only warehouse exploration surface — discovery, inspection, and execution each earn their place. A fourth tool (e.g. sample rows or schema listing) could add value, but nothing here is redundant.

Completeness4/5

The core read-only lifecycle — find tables, understand their columns, and run SELECT/WITH queries — is fully covered, and query acts as a universal escape hatch for anything not directly supported. Minor gaps like previewing sample rows or listing distinct schemas are workable via SQL, though write operations are intentionally absent.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues