Skip to main content
Glama
pab1it0

adx-mcp-server

get_table_schema

Retrieve the schema of a specified table in Azure Data Explorer, including column names, data types, and metadata.

Instructions

Retrieves the schema information for a specified table in the Azure Data Explorer database, including column names, data types, and other schema-related metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the get_table_schema tool. Retrieves schema information for a specified ADX table by executing '{table_name} | getschema' query. Uses validate_table_name for injection protection, get_kusto_client for connection, and format_query_results for output formatting.
    @mcp.tool(description="Retrieves the schema information for a specified table in the Azure Data Explorer database, including column names, data types, and other schema-related metadata.")
    async def get_table_schema(table_name: str) -> List[Dict[str, Any]]:
        """Get schema information for a specific table."""
        table_name = validate_table_name(table_name)
        logger.info("Getting table schema", table_name=table_name, database=config.database)
    
        if not config.cluster_url or not config.database:
            logger.error("Missing ADX configuration")
            raise ValueError("Azure Data Explorer configuration is missing. Please set ADX_CLUSTER_URL and ADX_DATABASE environment variables.")
    
        try:
            client = get_kusto_client()
            query = f"{table_name} | getschema"
            result_set = client.execute(config.database, query)
            results = format_query_results(result_set)
            logger.info("Schema retrieved successfully", table_name=table_name, column_count=len(results))
            return results
        except Exception as e:
            logger.error("Failed to get table schema", table_name=table_name, error=str(e), exception_type=type(e).__name__)
            raise
  • The tool is registered via the @mcp.tool decorator from FastMCP, which makes it available as an MCP tool with the given description.
    @mcp.tool(description="Retrieves the schema information for a specified table in the Azure Data Explorer database, including column names, data types, and other schema-related metadata.")
  • Helper function that validates table names against a regex pattern to prevent KQL injection attacks. Called at line 246 before executing the schema query.
    def validate_table_name(table_name: str) -> str:
        """Validate a KQL table name to prevent injection attacks.
    
        Allows simple identifiers (my_table) and dot-qualified names (database.table).
        Rejects any characters that could enable KQL injection.
        """
        if not table_name or not table_name.strip():
            raise ValueError("Table name cannot be empty")
        table_name = table_name.strip()
        if not _TABLE_NAME_PATTERN.match(table_name):
            raise ValueError(
                f"Invalid table name: '{table_name}'. "
                "Table names must contain only letters, digits, underscores, "
                "and dots (for qualified names like 'database.table')."
            )
        return table_name
  • Helper that creates and configures an Azure Kusto client with appropriate credentials (WorkloadIdentity or DefaultAzureCredential). Used at line 254 to execute the schema query.
    def get_kusto_client() -> KustoClient:
        """
        Create and configure a Kusto client with appropriate Azure credentials.
    
        Prioritizes WorkloadIdentityCredential when running in AKS with workload identity,
        falls back to DefaultAzureCredential for other authentication methods.
    
        Returns:
            KustoClient: Configured Kusto client instance
        """
        tenant_id = os.environ.get('AZURE_TENANT_ID')
        client_id = os.environ.get('AZURE_CLIENT_ID')
        token_file_path = os.environ.get('ADX_TOKEN_FILE_PATH', '/var/run/secrets/azure/tokens/azure-identity-token')
    
        if tenant_id and client_id:
            logger.info(
                "Using WorkloadIdentityCredential",
                client_id=client_id,
                tenant_id=tenant_id,
                token_file_path=token_file_path
            )
            try:
                credential = WorkloadIdentityCredential(
                    tenant_id=tenant_id,
                    client_id=client_id,
                    token_file_path=token_file_path
                )
            except Exception as e:
                logger.warning(
                    "Failed to initialize WorkloadIdentityCredential, falling back",
                    error=str(e),
                    exception_type=type(e).__name__
                )
                credential = DefaultAzureCredential()
        else:
            logger.info("Using DefaultAzureCredential (missing WorkloadIdentity credentials)")
            credential = DefaultAzureCredential()
    
        try:
            kcsb = KustoConnectionStringBuilder.with_azure_token_credential(
                connection_string=config.cluster_url,
                credential=credential
            )
            client = KustoClient(kcsb)
            logger.debug("Kusto client initialized successfully", cluster_url=config.cluster_url)
            return client
        except Exception as e:
            logger.error(
                "Failed to create Kusto client",
                error=str(e),
                exception_type=type(e).__name__,
                cluster_url=config.cluster_url
            )
            raise
  • Helper that formats raw Kusto query results into a list of dictionaries with column names as keys. Used at line 257 to process the schema results.
    def format_query_results(result_set) -> List[Dict[str, Any]]:
        """
        Format Kusto query results into a list of dictionaries.
    
        Args:
            result_set: Raw result set from KustoClient
    
        Returns:
            List of dictionaries with column names as keys
        """
        if not result_set or not result_set.primary_results:
            logger.debug("Empty or null result set received")
            return []
    
        try:
            primary_result = result_set.primary_results[0]
            columns = [col.column_name for col in primary_result.columns]
    
            formatted_results = []
            for row in primary_result.rows:
                record = {}
                for i, value in enumerate(row):
                    record[columns[i]] = value
                formatted_results.append(record)
    
            logger.debug("Query results formatted", row_count=len(formatted_results), columns=columns)
            return formatted_results
        except Exception as e:
            logger.error(
                "Error formatting query results",
                error=str(e),
                exception_type=type(e).__name__
            )
            raise
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It states the action but does not mention read-only safety, error handling (e.g., if table does not exist), or any prerequisites. For a read operation, minimal but still insufficient given zero annotation coverage.

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?

Single sentence that is concise and directly states the purpose. No wasted words, but could be slightly more structured (e.g., separating purpose and details). Still effective and efficient.

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 presence of output schema, description need not explain return values. For a simple one-parameter tool, the description covers the core function but misses usage guidelines and parameter details. Minimal viable but with clear gaps.

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

Parameters2/5

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

Input schema has one parameter (table_name) with 0% description coverage. The tool description does not elaborate on table_name format, expected values, or constraints. With low schema coverage, the description should compensate but fails to add meaning beyond the parameter name.

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

Purpose5/5

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

Description clearly states the verb 'retrieves', the resource 'schema information for a specified table', and includes specifics like 'column names, data types, and other schema-related metadata'. It easily distinguishes from siblings like 'execute_query' (runs queries) and 'list_tables' (lists tables).

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?

No guidance on when to use this tool versus alternatives. For example, it does not explain that this is for schema metadata only, while 'get_table_details' might include more. Lacks any explicit context or exclusion criteria.

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/pab1it0/adx-mcp-server'

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