Skip to main content
Glama
aliyun

Hologres MCP Server

Official
by aliyun

get_hg_query_plan

Analyze SQL query execution plans in Hologres databases to optimize performance and troubleshoot issues.

Instructions

Get query plan for a SQL query in Hologres database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe SQL query to analyze in Hologres database

Implementation Reference

  • Specific handler logic for get_hg_query_plan tool: extracts the query argument, validates it, and prefixes the SQL with 'EXPLAIN ' before delegating to handle_call_tool.
    elif name == "get_hg_query_plan":
        query = arguments.get("query")
        if not query:
            raise ValueError("Query is required")
        query = f"EXPLAIN {query}"
  • Registers the 'get_hg_query_plan' tool in the MCP server's list_tools() function, including its name, description, and input schema.
    Tool(
        name="get_hg_query_plan",
        description="Get query plan for a SQL query in Hologres database",
        inputSchema={
            "type": "object",
            "properties": {
                "query": {
                    "type": "string",
                    "description": "The SQL query to analyze in Hologres database"
                }
            },
            "required": ["query"]
        }
    ),
  • Pydantic input schema definition for the get_hg_query_plan tool, requiring a 'query' string.
    inputSchema={
        "type": "object",
        "properties": {
            "query": {
                "type": "string",
                "description": "The SQL query to analyze in Hologres database"
            }
        },
        "required": ["query"]
    }
  • Helper function that executes the prepared SQL query (EXPLAIN <user_query>) on the Hologres database, formats the result as CSV-like text, and handles errors.
    def handle_call_tool(tool_name, query, serverless = False):
        """Handle callTool method."""
        config = get_db_config()
        try:
            with connect_with_retry() as conn:
                with conn.cursor() as cursor:
    
                    # 特殊处理 serverless computing 查询
                    if serverless:
                        cursor.execute("set hg_computing_resource='serverless'")
                    
                    # Execute the query
                    cursor.execute(query)
                    
                    # 特殊处理 ANALYZE 命令
                    if tool_name == "gather_hg_table_statistics":
                        return f"Successfully {query}"
                    
                    # 处理其他有返回结果的查询
                    if cursor.description:  # SELECT query
                        columns = [desc[0] for desc in cursor.description]
                        rows = cursor.fetchall()
                        result = [",".join(map(str, row)) for row in rows]
                        return "\n".join([",".join(columns)] + result)
                    elif tool_name == "execute_dml_sql":  # Non-SELECT query
                        row_count = cursor.rowcount
                        return f"Query executed successfully. {row_count} rows affected."
                    else:
                        return "Query executed successfully"
        except Exception as e:
            return f"Error executing query: {str(e)}"
  • Helper function to establish a connection to the Hologres database with retry logic, used by handle_call_tool.
    def connect_with_retry(retries=3):
        attempt = 0
        err_msg = ""
        while attempt <= retries:
            try:
                config = get_db_config()
                conn = psycopg.connect(**config)
                conn.autocommit = True
                with conn.cursor() as cursor:
                    cursor.execute("SELECT 1;")
                    cursor.fetchone()
                return conn
            except psycopg.Error as e:
                err_msg = f"Connection failed: {e}"
                attempt += 1
                if attempt <= retries:
                    print(f"Retrying connection (attempt {attempt + 1} of {retries + 1})...")
                    time.sleep(5)  # 等待 2 秒后再次尝试连接
        raise psycopg.Error(f"Failed to connect to Hologres database after retrying: {err_msg}")
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 'Get[s] query plan', implying a read-only operation, but doesn't clarify if it requires specific permissions, whether it's safe for production use, what the output format is, or any rate limits. This leaves significant gaps for an agent to understand how to invoke it effectively.

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 with no wasted words, making it highly concise and front-loaded. It efficiently communicates the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given the complexity of database query analysis tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'query plan' entails, how the result is structured, or any behavioral traits like error handling, making it inadequate for an agent to use confidently without additional context.

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

Parameters3/5

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

The input schema has 100% description coverage, with the parameter 'query' documented as 'The SQL query to analyze in Hologres database'. The description adds no additional semantic details beyond this, such as query syntax requirements or examples, so it meets the baseline for high schema coverage without extra value.

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 verb 'Get' and the resource 'query plan for a SQL query in Hologres database', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_hg_execution_plan', which might cause confusion about the distinction between a query plan and an execution plan.

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. With siblings like 'execute_hg_select_sql' and 'get_hg_execution_plan', there's no indication of whether this is for analysis, debugging, or optimization, or any prerequisites for usage.

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/aliyun/alibabacloud-hologres-mcp-server'

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