Skip to main content
Glama
blitzstermayank

Teradata MCP Server

dba_tableSpace

Retrieve table space usage for specific tables or entire databases in Teradata to monitor storage allocation and optimize database performance.

Instructions

Get table space used for a table if table name is provided or get table space for all tables in a database if a database name is provided."

Arguments: database_name - database name table_name - table name

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_nameNo
table_nameNo

Implementation Reference

  • The core handler function for the 'dba_tableSpace' tool. It queries the DBC.AllSpaceV view to retrieve current and peak permanent space usage, skew percentage for specified table(s) in a database or all tables, based on optional database_name and table_name parameters. Returns formatted JSON data with metadata.
    def handle_dba_tableSpace(conn: TeradataConnection, database_name: str | None = None, table_name: str | None = None, *args, **kwargs):
        """
        Get table space used for a table if table name is provided or get table space for all tables in a database if a database name is provided."
    
        Arguments:
          database_name - database name
          table_name - table name
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_dba_tableSpace: Args: database_name: {database_name}, table_name: {table_name}")
    
        with conn.cursor() as cur:
            if not database_name and not table_name:
                logger.debug("No database or table name provided, returning all tables and space information.")
                rows = cur.execute("""SELECT DatabaseName, TableName, SUM(CurrentPerm) AS CurrentPerm1, SUM(PeakPerm) as PeakPerm
                ,CAST((100-(AVG(CURRENTPERM)/MAX(NULLIFZERO(CURRENTPERM))*100)) AS DECIMAL(5,2)) as SkewPct
                FROM DBC.AllSpaceV
                GROUP BY DatabaseName, TableName
                ORDER BY CurrentPerm1 desc;""")
            elif not database_name:
                logger.debug(f"No database name provided, returning all space information for table: {table_name}.")
                rows = cur.execute(f"""SELECT DatabaseName, TableName, SUM(CurrentPerm) AS CurrentPerm1, SUM(PeakPerm) as PeakPerm
                ,CAST((100-(AVG(CURRENTPERM)/MAX(NULLIFZERO(CURRENTPERM))*100)) AS DECIMAL(5,2)) as SkewPct
                FROM DBC.AllSpaceV
                WHERE TableName = '{table_name}'
                GROUP BY DatabaseName, TableName
                ORDER BY CurrentPerm1 desc;""")
            elif not table_name:
                logger.debug(f"No table name provided, returning all tables and space information for database: {database_name}.")
                rows = cur.execute(f"""SELECT TableName, SUM(CurrentPerm) AS CurrentPerm1, SUM(PeakPerm) as PeakPerm
                ,CAST((100-(AVG(CURRENTPERM)/MAX(NULLIFZERO(CURRENTPERM))*100)) AS DECIMAL(5,2)) as SkewPct
                FROM DBC.AllSpaceV
                WHERE DatabaseName = '{database_name}'
                GROUP BY TableName
                ORDER BY CurrentPerm1 desc;""")
            else:
                logger.debug(f"Database name: {database_name}, Table name: {table_name}, returning space information for this table.")
                rows = cur.execute(f"""SELECT DatabaseName, TableName, SUM(CurrentPerm) AS CurrentPerm1, SUM(PeakPerm) as PeakPerm
                ,CAST((100-(AVG(CURRENTPERM)/MAX(NULLIFZERO(CURRENTPERM))*100)) AS DECIMAL(5,2)) as SkewPct
                FROM DBC.AllSpaceV
                WHERE DatabaseName = '{database_name}' AND TableName = '{table_name}'
                GROUP BY DatabaseName, TableName
                ORDER BY CurrentPerm1 desc;""")
    
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "dba_tableSpace",
                "database_name": database_name,
                "table_name": table_name,
                "total_tables": len(data)
            }
            logger.debug(f"Tool: handle_dba_tableSpace: 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. It describes the tool's behavior (conditional fetching based on input) and output format ('formatted response with query results + metadata'), but lacks details on permissions, rate limits, error handling, or whether it's read-only/destructive. For a tool with no annotation coverage, this is a significant gap in behavioral disclosure.

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?

The description is appropriately sized and front-loaded: the first sentence clearly states the tool's purpose and logic. The additional 'Arguments' and 'Returns' sections are concise but redundant with the schema and output description. Overall, it's efficient with minimal waste.

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 no annotations, 0% schema coverage, and no output schema, the description provides basic purpose and conditional logic but lacks completeness. It doesn't cover parameter details, behavioral traits like safety or performance, or output specifics beyond a vague 'formatted response'. For a tool with two parameters and no structured support, this is adequate but has 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?

Schema description coverage is 0%, so the schema provides no parameter details. The description adds minimal semantics: it explains that 'database_name' and 'table_name' are used conditionally to fetch space for all tables or a specific table. However, it doesn't specify format requirements, constraints, or interactions between parameters (e.g., what happens if both are provided), leaving key aspects undocumented.

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 table space used for a table if table name is provided or get table space for all tables in a database if a database name is provided.' It specifies the verb ('get') and resource ('table space'), and distinguishes between two modes based on input. However, it doesn't explicitly differentiate from sibling tools like 'dba_databaseSpace' or 'dba_systemSpace', which likely handle different space metrics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage guidelines by stating the conditional logic: use table_name for a specific table's space, or database_name for all tables in a database. However, it doesn't provide explicit when-to-use vs. alternatives (e.g., compared to 'dba_databaseSpace' for database-level space or 'base_tableUsage' for other table metrics), nor does it mention prerequisites or exclusions.

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/blitzstermayank/MCP'

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