Skip to main content
Glama
rickyb30

DataPilot MCP Server

by rickyb30

get_warehouse_status

Check current Snowflake warehouse, database, and schema operational status to monitor system health and availability.

Instructions

Get current warehouse, database, and schema status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'get_warehouse_status', decorated with @mcp.tool(). It initializes the Snowflake client and delegates to client.get_warehouse_status() to retrieve current warehouse, database, and schema.
    @mcp.tool()
    async def get_warehouse_status(ctx: Context) -> Dict[str, Any]:
        """Get current warehouse, database, and schema status"""
        await ctx.info("Getting current warehouse status...")
        
        try:
            client = await get_snowflake_client()
            status = await client.get_warehouse_status()
            await ctx.info("Retrieved warehouse status")
            return status
            
        except Exception as e:
            logger.error(f"Error getting warehouse status: {str(e)}")
            await ctx.error(f"Failed to get warehouse status: {str(e)}")
            return {}
  • Supporting method in SnowflakeClient class that executes the SQL query to fetch and format the current warehouse, database, and schema status.
    async def get_warehouse_status(self) -> Dict[str, Any]:
        """Get current warehouse status"""
        result = await self.execute_query("SELECT CURRENT_WAREHOUSE(), CURRENT_DATABASE(), CURRENT_SCHEMA()")
        if result.success and result.data:
            row = result.data[0]
            return {
                'current_warehouse': row.get('CURRENT_WAREHOUSE()', ''),
                'current_database': row.get('CURRENT_DATABASE()', ''),
                'current_schema': row.get('CURRENT_SCHEMA()', '')
            }
        return {}
  • src/main.py:254-254 (registration)
    The @mcp.tool() decorator registers the get_warehouse_status function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves status information but doesn't specify what 'status' entails (e.g., operational health, usage metrics, configuration), whether it's real-time or cached, or any authentication or rate limit considerations. This leaves significant gaps for an agent to understand the tool's behavior.

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

Conciseness5/5

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

The description is a single, clear sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resources, making it efficient and easy to parse for an agent.

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 has 0 parameters, 100% schema coverage, and an output schema exists, the description is minimally adequate. However, it lacks details on what 'status' includes, which could be crucial for usage. With no annotations and a vague resource scope, more context would improve completeness for a status-checking tool.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here, but it could have clarified if any implicit parameters (like context or filters) are involved. Since there are no parameters, a baseline of 4 is applied.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Get') and resources ('warehouse, database, and schema status'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_warehouses' or 'list_databases', which focus on listing rather than retrieving status information.

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, context, or comparisons to siblings like 'list_warehouses' (which might list warehouses without status details) or 'analyze_query_results' (which could involve status indirectly).

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/rickyb30/datapilot-mcp-server'

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