redshift-utils-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | AWS region for Data API and Secrets Manager. | |
| AWS_PROFILE | No | AWS profile name to use from your credentials file (~/.aws/...). | |
| REDSHIFT_DATABASE | Yes | The name of the database to connect to. | |
| AWS_DEFAULT_REGION | No | Alternative to AWS_REGION for specifying the AWS region. | |
| REDSHIFT_CLUSTER_ID | Yes | Your Redshift cluster identifier. | |
| REDSHIFT_SECRET_ARN | Yes | AWS Secrets Manager ARN for Redshift credentials. |
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 |
|---|---|
| handle_check_cluster_healthA | Performs a health assessment of the Redshift cluster. |
| handle_diagnose_locksA | Identifies active lock contention in the cluster. |
| handle_diagnose_query_performanceA | Analyzes a specific query's execution performance. |
| handle_execute_ad_hoc_queryA | Executes an arbitrary SQL query provided by the user via Redshift Data API. |
| handle_get_table_definitionA | Retrieves the DDL (Data Definition Language) statement for a specific table. |
| handle_inspect_tableA | Retrieves detailed information about a specific Redshift table. |
| handle_monitor_workloadA | Analyzes cluster workload patterns over a specified time window. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| run_health_check | Guides the agent to perform a health check of the Redshift cluster. Args: level: Level of detail ('basic' or 'full'). Default: 'basic'. |
| analyze_slow_query | Guides the agent to analyze the performance of a specific Redshift query. Args: query_id: The numeric ID of the query to analyze. |
| check_table_health | Guides the agent to assess the health, design, and maintenance status of a specific table. Args: schema_name: The schema name of the table. table_name: The name of the table. |
| find_blocking_locks | Guides the agent to identify current lock contention and blocking sessions. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| redshift://schemas | |
| redshift://wlm/configuration |
TDQS
Scored across 7 tools
Each tool has a distinct purpose with clear boundaries: cluster health assessment, lock diagnosis, query performance analysis, ad-hoc query execution, table definition retrieval, table inspection, and workload monitoring. There is no functional overlap between tools, and the descriptions clearly differentiate their specific use cases.
All tools follow a 'handle_verb_noun' prefix pattern, which provides some consistency. However, the verb choices are mixed ('check', 'diagnose', 'execute', 'get', 'inspect', 'monitor'), making the naming somewhat inconsistent in terms of action semantics. The structure is predictable but the verb selection lacks uniformity.
With 7 tools, this server is well-scoped for Redshift cluster diagnostics and management. Each tool serves a specific, valuable function in the domain, and there are no redundant or trivial tools. The count is appropriate for covering key operational and troubleshooting tasks without being overwhelming.
The toolset covers essential diagnostic and operational areas for Redshift: health checks, lock analysis, query performance, ad-hoc queries, table definitions, table inspection, and workload monitoring. Minor gaps exist, such as lack of tools for cluster configuration changes, user/role management, or backup operations, but core diagnostic workflows are well-covered.