Qora
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | development, production, or test | development |
| LOG_LEVEL | No | Logging level | |
| TRANSPORT | No | stdio for local AI apps or http for web access | stdio |
| LOG_PRETTY | No | Make logs easier to read locally | |
| DATABASE_URL | Yes | PostgreSQL connection string. Use a read-only database user. | |
| ALLOWED_HOSTS | No | Hosts allowed to access the HTTP endpoint |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_schemasA | List database schemas the agent can see (system schemas excluded). Call this first to discover which schemas exist, then list_tables / describe_table. |
| list_tablesA | List tables and views the agent can query. Optionally filter by schema. Always call this (or describe_table) before writing a query against an unfamiliar table. |
| describe_tableA | Get column names, data types, and nullability for a specific table. Call this before querying a table you haven't seen the schema for. |
| run_queryA | Run a read-only SQL SELECT against Postgres. Only SELECT is permitted — writes, DDL, and multi-statement queries are rejected. Results capped at 1000 rows and returned as JSON ({ columns, rowCount, rows }). Prefer GROUP BY / aggregation over raw dumps. Always qualify table names with schema, e.g. |
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 4 tools
Each tool has a clearly distinct purpose: discovering schemas, listing tables, describing table schemas, and executing queries. No overlap or ambiguity.
All tools follow a consistent verb_noun pattern (list_schemas, list_tables, describe_table, run_query), making the naming predictable and clean.
With 4 tools, the set is well-scoped for a read-only database exploration and querying server. Each tool is necessary and sufficient for the core workflow.
The surface covers the full discovery-to-query lifecycle: schema discovery, table listing, schema introspection, and read-only query execution. No essential operations are missing for the stated purpose.