Skip to main content
Glama
santosh07401

Redshift MCP Server

by santosh07401

redshift_connection_status

Check the connection status of Amazon Redshift databases to verify connectivity and troubleshoot issues.

Instructions

Check the Redshift connection status.

Returns:
    Connection status information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'redshift_connection_status' tool. It is registered via @mcp.tool() decorator and checks the Redshift connection status, returning JSON with status details or error.
    @mcp.tool()
    def redshift_connection_status() -> str:
        """
        Check the Redshift connection status.
        
        Returns:
            Connection status information
        """
        try:
            with get_connection() as conn:
                return json.dumps({
                    "status": "connected",
                    "host": REDSHIFT_HOST,
                    "port": REDSHIFT_PORT,
                    "database": REDSHIFT_DATABASE
                }, indent=2)
        except Exception as e:
            return json.dumps({
                "status": "disconnected",
                "error": str(e)
            }, indent=2)
  • Supporting helper function used by the tool to establish the database connection.
    def get_connection():
        """Create a connection to Redshift or local Postgres."""
        try:
            # If host is localhost and port is 5432, assume local Postgres for testing
            if REDSHIFT_HOST == "localhost" and REDSHIFT_PORT == 5432:
                import psycopg2
                return psycopg2.connect(
                    host=REDSHIFT_HOST,
                    port=REDSHIFT_PORT,
                    database=REDSHIFT_DATABASE,
                    user=REDSHIFT_USER,
                    password=REDSHIFT_PASSWORD
                )
            else:
                return redshift_connector.connect(
                    host=REDSHIFT_HOST,
                    port=REDSHIFT_PORT,
                    database=REDSHIFT_DATABASE,
                    user=REDSHIFT_USER,
                    password=REDSHIFT_PASSWORD
                )
        except Exception as e:
            logger.error(f"Connection error: {e}")
            raise
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Returns: Connection status information,' which hints at a read-only operation, but doesn't specify what that information includes (e.g., success/failure, latency, error details) or any behavioral traits like rate limits, authentication needs, or side effects. For a tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short sentences, front-loading the purpose and then stating the return. There's no wasted text, and it's appropriately sized for a simple tool. However, the second sentence could be more informative, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, output schema exists), the description is somewhat complete but has gaps. It states the purpose and return, but lacks details on what 'connection status information' entails, which the output schema might cover. With no annotations, it should provide more behavioral context, but the output schema reduces the need to explain return values fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond the schema, and it correctly doesn't mention any. Baseline 4 is appropriate for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool's purpose as 'Check the Redshift connection status,' which is a clear verb+resource combination. However, it doesn't differentiate this from sibling tools like redshift_query or redshift_list_tables, which might also involve connection checks implicitly. The purpose is clear but lacks sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as whether a connection must be established first, or contrast it with siblings like redshift_query that might also test connectivity. There's no explicit when/when-not or alternative tool recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/santosh07401/redshift-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server