mnemiq
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNEMIQ_PG_DSN | Yes | PostgreSQL DSN connection string (e.g., postgresql://user:pass@host:5432/db). | |
| MNEMIQ_LLM_MODEL | Yes | The model name to use for the LLM. | |
| MNEMIQ_AUTHZ_PATH | No | Path to a policy file granting objects to roles. Optional; without it the engine grants nothing and defers. | |
| MNEMIQ_LLM_API_KEY | Yes | The API key for the LLM. | |
| MNEMIQ_LLM_BASE_URL | Yes | The base URL for the LLM API. |
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 |
|---|---|
| db_readA | Answer a natural-language question over the database (read-only). Returns the answer, the SQL run, and an auditable trace; defers honestly when it cannot answer. mode: 'instant' (cheapest, no retries), 'thinking' (default, self-repairing), or 'deep' (5 candidates + judge + agreement gate -- highest precision, ~6x cost). |
| db_writeA | Execute a single INSERT/UPDATE/DELETE (read/write governed separately from db_read). Refused by default: a write runs only when the identity has a write grant AND the deployment enabled writes. DDL and multi-statement input are never executed. Returns {approved, target, rows_affected, refusal, sql}; a governance plane records the result. |
| get_schemaA | List the tables you are allowed to query. |
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 3 tools
The three tools have clearly distinct purposes: db_read handles read-only queries, db_write handles mutations with explicit governance, and get_schema provides metadata. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent snake_case pattern with clear action-oriented verbs: db_read, db_write, and get_schema. The naming convention is uniform and predictable, with get_schema aligning to the same verb-first style.
Three tools is well-scoped for a database access server, covering the essential operations (read, write, schema) without unnecessary bloat. Each tool earns its place and the count is within the ideal range.
The tool surface fully covers the core domain of database access: reading via natural language, writing with safety controls, and schema introspection. There are no obvious gaps for typical query workflows, and the write tool handles INSERT, UPDATE, and DELETE, completing the CRUD cycle.