Skip to main content
Glama
p2k3m

MCP Vertica

by p2k3m

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VERTICA_SSLNoEnable SSL/TLS supportfalse
VERTICA_HOSTNoThe Vertica database hostlocalhost
VERTICA_PORTNoThe Vertica database port5433
VERTICA_USERNoThe Vertica database userdbadmin
VERTICA_DATABASENoThe Vertica database nameVMart
VERTICA_PASSWORDNoThe Vertica database password
ALLOW_DDL_OPERATIONNoAllow DDL operationsfalse
ALLOW_DELETE_OPERATIONNoAllow DELETE operationsfalse
ALLOW_INSERT_OPERATIONNoAllow INSERT operationsfalse
ALLOW_UPDATE_OPERATIONNoAllow UPDATE operationsfalse
SCHEMA_DDL_PERMISSIONSNoSchema-specific DDL permissions (format: schema1:true,schema2:false)
VERTICA_CONNECTION_LIMITNoConnection pooling limit10
SCHEMA_DELETE_PERMISSIONSNoSchema-specific DELETE permissions (format: schema1:true,schema2:false)
SCHEMA_INSERT_PERMISSIONSNoSchema-specific INSERT permissions (format: schema1:true,schema2:false)
SCHEMA_UPDATE_PERMISSIONSNoSchema-specific UPDATE permissions (format: schema1:true,schema2:false)
VERTICA_SSL_REJECT_UNAUTHORIZEDNoSSL reject unauthorized connectionstrue

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
execute_queryC

Execute a SQL query and return the results.

Args:
    ctx: FastMCP context for progress reporting and logging
    query: SQL query to execute
    database: Optional database name to execute the query against

Returns:
    Query results as a string
stream_queryC

Execute a SQL query and return the results in batches as a single string.

Args:
    ctx: FastMCP context for progress reporting and logging
    query: SQL query to execute
    batch_size: Number of rows to fetch at once

Returns:
    Query results as a concatenated string
copy_dataC

Copy data into a Vertica table using COPY command.

Args:
    ctx: FastMCP context for progress reporting and logging
    schema: vertica schema to execute the copy against
    table: Target table name
    data: List of rows to insert

Returns:
    Status message indicating success or failure
get_table_structureB

Get the structure of a table including columns, data types, and constraints.

Args:
    ctx: FastMCP context for progress reporting and logging
    table_name: Name of the table to inspect
    schema: Schema name (default: public)

Returns:
    Table structure information as a string
list_indexesB

List all indexes for a specific table.

Args:
    ctx: FastMCP context for progress reporting and logging
    table_name: Name of the table to inspect
    schema: Schema name (default: public)

Returns:
    Index information as a string
list_viewsB

List all views in a schema.

Args:
    ctx: FastMCP context for progress reporting and logging
    schema: Schema name (default: public)

Returns:
    View information as a string

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity: copy_data handles data insertion, execute_query and stream_query handle query execution with different output methods, get_table_structure inspects table schema, list_indexes lists indexes, and list_views lists views. The descriptions clearly differentiate their functions, making misselection unlikely.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (copy_data, execute_query, get_table_structure, list_indexes, list_views, stream_query). The naming is uniform throughout, using snake_case and clear action-object pairs, making the tool set predictable and easy to understand.

Tool Count4/5

With 6 tools, the count is well-scoped for a database server, covering core operations like querying, data insertion, and schema inspection. It feels slightly lean but reasonable, as it includes essential functions without being overwhelming. A few more tools for updates or deletions might enhance coverage, but it's not a significant gap.

Completeness3/5

The tool set covers query execution, data copying, and schema inspection well, but there are notable gaps in CRUD operations. It lacks tools for updating or deleting data, creating or modifying tables, or managing users/roles. This could cause agent failures for common database workflows beyond basic querying and insertion.

Maintenance

ActivityInactive
ResponsivenessNo issues