Skip to main content
Glama
blitzstermayank

Teradata MCP Server

base_tableUsage

Measure table and view usage by users in a Teradata schema to identify active database objects and their value through SQL analysis.

Instructions

Measure the usage of a table and views by users in a given schema, this is helpful to infer what database objects are most actively used or drive most value via SQLAlchemy, bind parameters if provided (prepared SQL), and return the fully rendered SQL (with literals) in metadata.

Arguments: database_name - Database name

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_nameNo

Implementation Reference

  • Handler function that implements the core logic for the 'base_tableUsage' tool. It executes a SQL query against DBC.DBQLObjTbl and DBC.DBQLogTbl to compute table usage frequency, recency, and ranking within a specified database.
    def handle_base_tableUsage(conn: TeradataConnection, database_name: str | None = None, *args, **kwargs):
        """
        Measure the usage of a table and views by users in a given schema, this is helpful to infer what database objects are most actively used or drive most value via SQLAlchemy, bind parameters if provided (prepared SQL), and return the fully rendered SQL (with literals) in metadata.
    
        Arguments:
          database_name - Database name
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
    
        logger.debug("Tool: handle_base_tableUsage: Args: database_name:")
        database_name_filter = f"AND objectdatabasename = '{database_name}'" if database_name else ""
    
        table_usage_sql="""
        LOCKING ROW for ACCESS
        sel
        DatabaseName
        ,TableName
        ,Weight as "QueryCount"
        ,100*"Weight" / sum("Weight") over(partition by 1) PercentTotal
        ,case
            when PercentTotal >=10 then 'High'
            when PercentTotal >=5 then 'Medium'
            else 'Low'
        end (char(6)) usage_freq
        ,FirstQueryDaysAgo
        ,LastQueryDaysAgo
    
        from
        (
            SELECT   TRIM(QTU1.TableName)  AS "TableName"
                    , TRIM(QTU1.DatabaseName)  AS "DatabaseName"
                    ,max((current_timestamp - CollectTimeStamp) day(4)) as "FirstQueryDaysAgo"
                    ,min((current_timestamp - CollectTimeStamp) day(4)) as "LastQueryDaysAgo"
                    , COUNT(DISTINCT QTU1.QueryID) as "Weight"
            FROM    (
                                SELECT   objectdatabasename AS DatabaseName
                                    , ObjectTableName AS TableName
                                    , QueryId
                                FROM DBC.DBQLObjTbl /* uncomment for DBC */
                                WHERE Objecttype in ('Tab', 'Viw')
                                {database_name_filter}
                                AND ObjectTableName IS NOT NULL
                                AND ObjectColumnName IS NULL
                                -- AND LogDate BETWEEN '2017-01-01' AND '2017-08-01' /* uncomment for PDCR */
                                --	AND LogDate BETWEEN current_date - 90 AND current_date - 1 /* uncomment for PDCR */
                                GROUP BY 1,2,3
                            ) AS QTU1
            INNER JOIN DBC.DBQLogTbl QU /* uncomment for DBC */
            ON QTU1.QueryID=QU.QueryID
            AND (QU.AMPCPUTime + QU.ParserCPUTime) > 0
    
            GROUP BY 1,2
        ) a
        order by PercentTotal desc
        qualify PercentTotal>0
        ;
    
        """
    
    
        with conn.cursor() as cur:
            rows = cur.execute(table_usage_sql.format(database_name_filter=database_name_filter))
            data = rows_to_json(cur.description, rows.fetchall())
        if len(data):
            info=f'This data contains the list of tables most frequently queried objects in database schema {database_name}'
        else:
            info=f'No tables have recently been queried in the database schema {database_name}.'
        metadata = {
            "tool_name": "handle_base_tableUsage",
            "database": database_name,
            "table_count": len(data),
            "comment": info
        }
        logger.debug(f"Tool: handle_base_tableUsage: metadata: {metadata}")
        return create_response(data, metadata)
  • Dynamic registration of Python handler functions as MCP tools. Strips 'handle_' prefix from function names to derive the tool name (e.g., 'handle_base_tableUsage' becomes 'base_tableUsage') and wraps with DB connection injection and QueryBand support.
    for name, func in all_functions.items():
        if not (inspect.isfunction(func) and name.startswith("handle_")):
            continue
        tool_name = name[len("handle_"):]
        if not any(re.match(p, tool_name) for p in config.get('tool', [])):
            continue
        wrapped = make_tool_wrapper(func)
        mcp.tool(name=tool_name, description=wrapped.__doc__)(wrapped)
        logger.info(f"Created tool: {tool_name}")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

No annotations provided, so description carries burden. It mentions use of SQLAlchemy and return of rendered SQL metadata, but does not explicitly state read-only behavior or potential side effects. Some transparency but incomplete.

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

Conciseness3/5

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

Description mixes purpose with implementation details (SQLAlchemy, bind parameters) and return metadata. Could be more concise; the first sentence is clear, but subsequent text adds redundancy.

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?

For a tool with one optional parameter and no output schema, description lacks detail on default behavior when database_name is null. Return format is vague ('formatted response with query results + metadata'). Leaves agent guessing.

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?

Only parameter is 'database_name' with schema coverage 0%. Description repeats 'Database name' without additional detail (e.g., format, required vs optional, behavior if omitted). Adds no value beyond schema.

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 measures usage of tables and views by users, helping infer active objects. It mentions arguments and returns, but does not specify what exact metrics are provided (e.g., query counts, user counts). Distinguished from siblings like base_tableAffinity.

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 siblings like dba_tableUsageImpact or base_tableAffinity. The description does not mention prerequisites, limitations, or alternatives.

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