Skip to main content
Glama
aliyun

Hologres MCP Server

Official
by aliyun

get_hg_execution_plan

Analyze SQL query performance in Hologres by retrieving execution plans with runtime statistics to identify optimization opportunities.

Instructions

Get actual execution plan with runtime statistics for a SQL query in Hologres database

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe SQL query to analyze in Hologres database

Implementation Reference

  • Registration of the get_hg_execution_plan tool, including its schema definition.
    Tool(
        name="get_hg_execution_plan",
        description="Get actual execution plan with runtime statistics 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"]
        }
    ),
  • Input schema for the get_hg_execution_plan tool.
    inputSchema={
        "type": "object",
        "properties": {
            "query": {
                "type": "string",
                "description": "The SQL query to analyze in Hologres database"
            }
        },
        "required": ["query"]
    }
  • Specific handler dispatch in call_tool function that wraps the input query with 'EXPLAIN ANALYZE' for execution plan.
        query = f"EXPLAIN ANALYZE {query}"
    elif name == "call_hg_procedure":
        procedure_name = arguments.get("procedure_name")
        arguments_list = arguments.get("arguments")
        if not procedure_name:
  • Generic helper function that connects to the database, executes the prepared query (EXPLAIN ANALYZE), fetches results, and formats the execution plan output.
    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)}"
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 mentions 'actual execution plan with runtime statistics', implying it may execute the query to gather runtime data, but does not specify if this is read-only, has side effects, requires permissions, or details on rate limits or output format. This leaves significant gaps in understanding 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized, making it easy to parse and understand quickly.

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 SQL execution analysis and the lack of annotations and output schema, the description is incomplete. It does not explain what the output includes (e.g., plan details, statistics format), potential impacts (e.g., if query execution occurs), or how it differs from similar tools, making it inadequate for full contextual understanding.

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' clearly documented. The description adds no additional semantic details beyond what the schema provides, such as query format constraints or examples. Thus, it meets the baseline score of 3, as the schema adequately covers parameter information.

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 resource ('actual execution plan with runtime statistics for a SQL query in Hologres database'), making the purpose specific and understandable. However, it does not explicitly differentiate from its sibling 'get_hg_query_plan', which might be a similar tool, leaving some ambiguity in distinguishing between them.

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, such as 'get_hg_query_plan' or other execution tools like 'execute_hg_select_sql'. There are no explicit instructions on prerequisites, context, or exclusions, leaving usage decisions unclear for an AI agent.

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