Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata

dba_tableSqlList

Retrieve SQL queries executed against a Teradata table within a specified timeframe to analyze database activity and monitor table usage patterns.

Instructions

Get a list of SQL run against a table in the last number of days.

Arguments: table_name - table name no_days - number of days

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
table_nameYes
no_daysNo

Implementation Reference

  • The core handler function implementing the 'dba_tableSqlList' tool. It executes a SQL query to retrieve recent queries against a specified table from Teradata's query log views (DBC.QryLogSqlV and DBC.QryLogV), formats the results using utility functions, and returns a structured response with metadata.
    def handle_dba_tableSqlList(conn: TeradataConnection, table_name: str, no_days: int | None = 7,  *args, **kwargs):
        """
        Get a list of SQL run against a table in the last number of days.
    
        Arguments:
          table_name - table name
          no_days - number of days
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_dba_tableSqlList: Args: table_name: {table_name}, no_days: {no_days}")
    
        with conn.cursor() as cur:
            if table_name == "":
                logger.debug("No table name provided")
            else:
                logger.debug(f"Table name provided: {table_name}, returning SQL queries for this table.")
                rows = cur.execute(f"""SELECT t1.QueryID, t1.ProcID, t1.CollectTimeStamp, t1.SqlTextInfo, t2.UserName
                FROM DBC.QryLogSqlV t1
                JOIN DBC.QryLogV t2
                ON t1.QueryID = t2.QueryID
                WHERE t1.CollectTimeStamp >= CURRENT_TIMESTAMP - INTERVAL '{no_days}' DAY
                AND t1.SqlTextInfo LIKE '%{table_name}%'
                ORDER BY t1.CollectTimeStamp DESC;""")
    
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "dba_tableSqlList",
                "table_name": table_name,
                "no_days": no_days,
                "total_queries": len(data)
            }
            logger.debug(f"Tool: handle_dba_tableSqlList: metadata: {metadata}")
            return create_response(data, metadata)
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 returns a 'formatted response with query results + metadata', which hints at output structure, but lacks details on permissions, rate limits, data freshness, or side effects. For a tool that queries SQL history, this is a significant gap in transparency.

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?

The description is structured with clear sections (purpose, arguments, returns) and is relatively concise. However, the 'Arguments' and 'Returns' sections are somewhat redundant with the input schema and could be more integrated. It avoids fluff but could be more front-loaded with critical information.

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 querying SQL history, lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It does not address key aspects like authentication needs, error handling, pagination, or how results are formatted. The tool's purpose is clear, but operational and behavioral details are insufficient for confident use.

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?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. It lists 'table_name' and 'no_days' with brief labels but adds minimal semantic context (e.g., no examples, constraints, or format details). The description does not clarify what 'table_name' entails (e.g., fully qualified name) or how 'no_days' defaults or behaves with null values, leaving gaps in understanding.

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: 'Get a list of SQL run against a table in the last number of days.' This specifies the verb ('Get a list'), resource ('SQL run against a table'), and temporal scope ('last number of days'). However, it does not explicitly differentiate this tool from sibling tools like 'dba_userSqlList' or 'sql_Retrieve_Cluster_Queries', which may offer similar functionality but for different scopes or purposes.

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 does not mention sibling tools like 'dba_userSqlList' (for user-specific SQL) or 'base_tableUsage' (for general table usage), nor does it specify prerequisites, exclusions, or contextual triggers. Usage is implied by the purpose but lacks explicit direction.

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/Teradata/teradata-mcp-server'

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