Skip to main content
Glama
avantifellows

Avanti Fellows PostgreSQL MCP Server

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AF_DB_HOSTYesThe database host
AF_DB_NAMEYesThe database name
AF_DB_PORTNoThe database port5432
AF_DB_USERYesThe database username
AF_DB_PASSWORDYesThe database password

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
queryA

Execute a read-only SQL query against the database.

Only SELECT queries are allowed. Use this to explore data,
debug issues, or validate assumptions about the data.

Args:
    sql: A SELECT query to execute

Returns:
    JSON array of results, or error message
list_tablesA

List all tables in the database.

Returns tables from all schemas (excluding system schemas).
Use this to discover what data is available.

Returns:
    JSON array of tables with schema, name, and type
describe_tableA

Get detailed schema information for a table.

Returns column names, types, nullability, and defaults.
Use this to understand table structure before querying.

Args:
    table_name: Name of the table
    schema_name: Schema name (default: public)

Returns:
    JSON with columns, primary keys, and foreign keys
sample_dataA

Get sample rows from a table.

Useful for understanding what data looks like without
writing a full query.

Args:
    table_name: Name of the table
    schema_name: Schema name (default: public)
    limit: Number of rows to return (default: 10, max: 100)

Returns:
    JSON array of sample rows
count_rowsA

Count rows in a table, optionally with a WHERE clause.

Args:
    table_name: Name of the table
    schema_name: Schema name (default: public)
    where: Optional WHERE clause (without 'WHERE' keyword)

Returns:
    JSON with count
search_columnsA

Search for columns by name across all tables.

Useful when you know a column name but not which table it's in.

Args:
    search_term: Partial column name to search for (case-insensitive)

Returns:
    JSON array of matching columns with their tables

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: count_rows counts rows, describe_table provides schema details, list_tables enumerates tables, query executes SQL, sample_data retrieves sample rows, and search_columns finds columns by name. The descriptions reinforce these unique functions, making misselection unlikely.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case, such as count_rows, describe_table, list_tables, query, sample_data, and search_columns. This uniformity makes the tool set predictable and easy to navigate for an agent.

Tool Count5/5

With 6 tools, the server is well-scoped for a PostgreSQL exploration and querying purpose. Each tool earns its place by covering essential database operations like discovery, inspection, and data retrieval without being overly complex or sparse.

Completeness4/5

The tool set provides strong coverage for exploring and querying a PostgreSQL database, including discovery (list_tables, search_columns), inspection (describe_table), and data retrieval (count_rows, sample_data, query). A minor gap is the lack of write operations (e.g., insert, update, delete), but this aligns with a read-only focus, and agents can work around it for analysis tasks.

Maintenance

ActivityMaintained
ResponsivenessNo issues