Conarium
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONARIUM_ANCHOR_SINK | No | Set to 'opentimestamps' to opt in to OpenTimestamps anchoring of the receipt chain. | |
| CONARIUM_NPM_REGISTRY | No | URL of an internal npm mirror for the startup update check. | |
| CONARIUM_SCAN_CHAR_CAP | No | Maximum number of characters to scan in a text field; longer fields are replaced with [MASKED_PII]. | |
| CONARIUM_AUDIT_HMAC_KEY | No | HMAC key for audit integrity. Set CONARIUM_AUDIT_SIGNING_KEY and/or CONARIUM_AUDIT_HMAC_KEY. | |
| CONARIUM_AUDIT_UNSIGNED | No | Set to '1' to allow unsigned audit entries for throwaway setups. Must be explicitly set if no signing or HMAC key is provided. | |
| CONARIUM_NO_UPDATE_CHECK | No | Set to '1' to disable the startup update check against the npm registry. | |
| CONARIUM_AUDIT_SIGNING_KEY | No | Path to an Ed25519 private PEM file used to sign audit receipts. Set CONARIUM_AUDIT_SIGNING_KEY and/or CONARIUM_AUDIT_HMAC_KEY. | |
| CONARIUM_AUDIT_TRUST_PUBKEYS | No | Comma or semicolon separated list of prior public PEMs used for key rotation. |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tablesA | List the database tables this gateway is allowed to expose. Read-only. Returns one entry per table with its connector, schema-qualified name and description; tables the policy denies are absent rather than marked, so this is the authoritative list of what any other tool here can reach. Call it before describe_table or query when the table names are not already known. Every call is written to the audit ledger, and to a signed receipt as well when a receipt sink is configured. |
| describe_tableA | Get the columns of one table: name, type and description. Read-only, and it returns structure only — no row is read, so nothing here is masked. Use it to write a correct query; use list_tables first if the table name is not known. A table the policy denies returns an error rather than an empty result. Every call is written to the audit ledger, and to a signed receipt as well when a receipt sink is configured. |
| queryA | Run one read-only SELECT against the company database. Only SELECT is allowed; anything else is refused before it reaches the database. Rows come back capped by the policy (maxRows, often lower than any LIMIT you write) and protected values arrive already replaced with [MASKED_PII] or [MASKED_SECRET] — the raw values never leave the gateway, so do not plan on receiving them. A refusal is a normal outcome, not a fault. Use search instead when there is no SELECT yet and the goal is to find text. Every call is written to the audit ledger, and to a signed receipt as well when a receipt sink is configured. |
| searchA | Find rows by a search term across the allowed tables — no SQL required. Read-only. Use it when the goal is to look up text and there is no SELECT yet; use query when a SELECT already exists. Returns matching rows under the same policy as query: capped by maxRows, with protected values already replaced by [MASKED_PII] or [MASKED_SECRET]. The policy decides which scopes are searchable at all. Every call is written to the audit ledger, and to a signed receipt as well when a receipt sink is configured. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| maindb schema | PostgreSQL Connector |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: list_tables for discovery, describe_table for schema, search for text lookup without SQL, and query for explicit SELECT statements. The description explicitly differentiates search vs query, eliminating ambiguity.
All tool names follow a consistent lowercase snake_case pattern with imperative verbs: search, list_tables, describe_table, query. This is a uniform and predictable style.
Four tools is well-scoped for a read-only database gateway: it covers table discovery, schema inspection, text search, and arbitrary SELECT queries without unnecessary bloat or gaps.
The surface is complete for its stated purpose: an agent can list tables, inspect schema, search for text, and execute read-only SQL. No dead ends or missing lifecycle operations are evident.