Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LLM_MODELNoLanguage model name for SQL generationqwen2.5-coder:3b
LLM_API_KEYNoAPI key for the LLM service (optional)
LLM_TIMEOUTNoTimeout in seconds for LLM requests60
DATABASE_URLYesPostgreSQL connection string (e.g., postgresql://user:password@localhost:5432/database_name)
LLM_BASE_URLNoBase URL of the OpenAI-compatible API (default Ollama endpoint)http://localhost:11434/v1
DB_CONNECT_TIMEOUTNoConnection timeout in seconds for PostgreSQL5

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
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tablesA

List the tables available in the configured read-only database.

describe_tableB

Return column metadata for a table.

generate_queryA

Turn a natural-language request into one read-only SQL statement.

run_readonly_queryA

Execute a single read-only SELECT or WITH query and return its rows.

execute_generated_queryA

DANGEROUS: generate SQL from a prompt and execute it immediately.

This executes model-generated SQL without a separate review step. Use generate_query and run_readonly_query instead when possible.

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 5 tools

Disambiguation4/5

Most tools are clearly distinct: schema inspection (list_tables, describe_table), SQL generation (generate_query), and query execution (run_readonly_query). execute_generated_query overlaps by combining generation and execution, but its DANGEROUS warning and guidance to prefer the separate steps mitigate confusion.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, with optional qualifiers like readonly and generated. The naming clearly indicates the action and target (list_tables, describe_table, generate_query, run_readonly_query, execute_generated_query).

Tool Count5/5

Five tools is well-scoped for a read-only database interface: schema exploration, query generation, exact query execution, and a dangerous combined shortcut. Each tool contributes a distinct capability without unnecessary bloat.

Completeness5/5

The tool surface covers the complete read-only workflow: see what tables exist, inspect schema, translate natural language to SQL, and execute read-only queries. The optional generate-and-execute tool also fills the convenience path without introducing an obvious dead end.

Maintenance

ActivityMaintained
ResponsivenessNo issues