Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Control local DBngin (TablePlus) database engines on Windows: list services, start/stop/restart PostgreSQL and Redis, inspect live status and read logs. Resolve services by 'name' plus optional 'type' (names can repeat across engine types) or by 'id' from list_services. Start/stop is implemented for postgresql and redis; other engine types support status probing only.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_servicesA

List all DBngin-managed local database services (PostgreSQL, Redis, MySQL, ...) with live running state detected by TCP port probing. Use this first to discover service names, types, ports and IDs before calling start_service / stop_service.

start_serviceA

Start a DBngin local database service. Supported engines: postgresql (postgres.exe spawned detached with the same command line as the DBngin app) and redis (hidden detached redis-server). Waits until the service port answers (up to 15s). Returns 'already_running' without failing if the service is up. Resolve the service by 'name' plus optional 'type' (names can repeat across engine types) or by 'id'.

stop_serviceA

Stop a DBngin local database service. PostgreSQL is stopped with 'pg_ctl stop -m fast'; Redis receives 'SHUTDOWN NOSAVE' via redis-cli (fallback: taskkill only if the port listener is redis-server.exe). Waits until the port stops answering (up to 15s). Returns 'already_stopped' without failing if the service is down.

restart_serviceA

Restart a DBngin local database service (stop_service followed by start_service). Supported engines: postgresql and redis. Use only when a restart is actually needed; for a stopped service, prefer start_service.

service_statusA

Detailed live status of one DBngin service: running state, PID, process name, port answering, Redis PING, uptime/started-at, and data/bin/log paths. Works for every engine type (detection is port-probe based for engines other than postgresql/redis).

get_logsA

Return the last N lines (default 50, max 1000) of a DBngin service log. PostgreSQL reads '/pg_log.log'; Redis reads the DBngin Engines/redis log file written when started through this server. Pass 'name' plus optional 'type' (or 'id') and 'lines'.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct role: lifecycle actions (start/stop/restart), discovery (list_services), diagnostics (service_status), and log retrieval. The only mild overlap is list_services vs service_status since both surface running state, but descriptions clarify the former is for discovery and the latter for detailed per-service inspection.

Naming Consistency4/5

All names are snake_case and mostly follow a verb_noun pattern (list_services, start_service, stop_service, restart_service, get_logs). Minor deviations: service_status puts the noun first instead of a verb, and get_logs uses a different verb style than list_services for a read operation.

Tool Count5/5

Six tools is well-scoped for a local database service manager, covering exactly the discovery, lifecycle, and diagnostics operations an agent needs. No tool feels redundant or superfluous.

Completeness4/5

The surface covers the full service lifecycle (list, start, stop, restart, status, logs) with no dead ends for managing existing services. Minor gaps exist — no tool to create/register a new service or edit configuration/data paths, but core operational workflows are fully supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues