Skip to main content
Glama
blitzstermayank

Teradata MCP Server

qlty_columnSummary

Analyze table columns to generate summary statistics for data quality assessment in Teradata databases.

Instructions

Get the column summary statistics for a table.

Arguments: database_name - name of the database table_name - table name to analyze

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_nameYes
table_nameYes

Implementation Reference

  • The handler function for the 'qlty_columnSummary' tool. It connects to Teradata, executes TD_ColumnSummary on the specified table (optionally qualified with database), converts results to JSON, adds metadata including the tool name, and returns a formatted response using create_response.
    def handle_qlty_columnSummary(conn: TeradataConnection, database_name: str | None, table_name: str, *args, **kwargs):
        """
        Get the column summary statistics for a table.
    
        Arguments:
          database_name - name of the database
          table_name - table name to analyze
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_qlty_columnSummary: Args: table_name: {database_name}.{table_name}")
    
        if database_name is not None:
                table_name = f"{database_name}.{table_name}"
        with conn.cursor() as cur:
            rows = cur.execute(f"select * from TD_ColumnSummary ( on {table_name} as InputTable using TargetColumns ('[:]')) as dt")
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "qlty_columnSummary",
                "database_name": database_name,
                "table_name": table_name,
                "rows": len(data)
            }
            logger.debug(f"Tool: handle_qlty_columnSummary: 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 mentions the return type ('formatted response with query results + metadata'), which adds some context, but fails to describe critical behaviors such as whether this is a read-only operation, performance implications, error handling, or data access permissions required.

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 states the purpose clearly, followed by structured sections for arguments and returns. There's minimal waste, though the 'Arguments' and 'Returns' sections could be integrated more fluidly into the narrative.

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 the tool's moderate complexity (2 parameters, no output schema, no annotations), the description is partially complete. It covers the basic purpose and parameters but lacks behavioral context (e.g., safety, performance) and usage guidelines. Without annotations or output schema, more detail on return values and operational constraints would improve completeness.

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?

Schema description coverage is 0%, so the description must compensate. It lists the two parameters ('database_name' and 'table_name') and briefly explains their purpose ('name of the database', 'table name to analyze'), adding basic semantics beyond the schema's titles. However, it doesn't provide details like format constraints, examples, or default behaviors for null values (e.g., 'database_name' can be null).

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 the column summary statistics for a table.' This specifies the verb ('Get'), resource ('column summary statistics'), and target ('for a table'). However, it doesn't explicitly differentiate from sibling tools like 'qlty_univariateStatistics' or 'qlty_distinctCategories', which likely provide related statistical analyses.

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 doesn't mention sibling tools like 'qlty_univariateStatistics' or 'base_tablePreview' that might serve similar or complementary purposes, nor does it specify prerequisites or exclusions for usage.

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