MCP Vertica
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VERTICA_SSL | No | Enable SSL/TLS support | false |
| VERTICA_HOST | No | The Vertica database host | localhost |
| VERTICA_PORT | No | The Vertica database port | 5433 |
| VERTICA_USER | No | The Vertica database user | dbadmin |
| VERTICA_DATABASE | No | The Vertica database name | VMart |
| VERTICA_PASSWORD | No | The Vertica database password | |
| ALLOW_DDL_OPERATION | No | Allow DDL operations | false |
| ALLOW_DELETE_OPERATION | No | Allow DELETE operations | false |
| ALLOW_INSERT_OPERATION | No | Allow INSERT operations | false |
| ALLOW_UPDATE_OPERATION | No | Allow UPDATE operations | false |
| SCHEMA_DDL_PERMISSIONS | No | Schema-specific DDL permissions (format: schema1:true,schema2:false) | |
| VERTICA_CONNECTION_LIMIT | No | Connection pooling limit | 10 |
| SCHEMA_DELETE_PERMISSIONS | No | Schema-specific DELETE permissions (format: schema1:true,schema2:false) | |
| SCHEMA_INSERT_PERMISSIONS | No | Schema-specific INSERT permissions (format: schema1:true,schema2:false) | |
| SCHEMA_UPDATE_PERMISSIONS | No | Schema-specific UPDATE permissions (format: schema1:true,schema2:false) | |
| VERTICA_SSL_REJECT_UNAUTHORIZED | No | SSL reject unauthorized connections | true |
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
| Name | Description |
|---|---|
| execute_queryC | Execute a SQL query and return the results. |
| stream_queryC | Execute a SQL query and return the results in batches as a single string. |
| copy_dataC | Copy data into a Vertica table using COPY command. |
| get_table_structureB | Get the structure of a table including columns, data types, and constraints. |
| list_indexesB | List all indexes for a specific table. |
| list_viewsB | List all views in a schema. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
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.
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.
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.
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.