Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata

qlty_rowsWithMissingValues

Identify and retrieve rows containing missing values in a specified Teradata table column to assess data quality and integrity.

Instructions

Get the rows with missing values in a table.

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

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
database_nameYes
table_nameYes
column_nameYes

Implementation Reference

  • Handler function executing the qlty_rowsWithMissingValues tool. It connects to Teradata, constructs the table reference, executes a query using TD_getRowsWithMissingValues to fetch rows with missing values in the specified column, formats the results, and returns a response with metadata.
    def handle_qlty_rowsWithMissingValues(
        conn: TeradataConnection,
        database_name: str | None,
        table_name: str,
        column_name: str,
        *args,
        **kwargs
    ):
        """
        Get the rows with missing values in a table.
    
        Arguments:
          database_name - name of the database
          table_name - table name to analyze
          column_name - column name to analyze
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_qlty_rowsWithMissingValues: Args: table_name: {database_name}.{table_name}, column_name: {column_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_getRowsWithMissingValues ( ON {table_name} AS InputTable USING TargetColumns ('[{column_name}]')) AS dt;")
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "qlty_rowsWithMissingValues",
                "database_name": database_name,
                "table_name": table_name,
                "column_name": column_name,
                "rows_with_missing_values": len(data)
            }
            logger.debug(f"Tool: handle_qlty_rowsWithMissingValues: 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 tool 'Get[s] the rows with missing values' but does not explain critical behaviors like whether it performs read-only operations, potential performance impacts, error handling, or output format details beyond 'formatted response with query results + metadata.' This leaves significant gaps in understanding how the tool behaves.

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 concise and well-structured, with a clear purpose statement followed by bullet points for arguments and returns. It avoids unnecessary verbosity, making it easy to scan. However, the lack of usage context or behavioral details means it could be more informative without sacrificing brevity.

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 tool's complexity (3 parameters, no annotations, no output schema), the description is incomplete. It covers the basic purpose and parameters but misses usage guidelines, behavioral traits, and detailed output expectations. For a data analysis tool, this leaves too many unknowns for effective use.

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?

The description lists the three parameters (database_name, table_name, column_name) and their roles, adding meaning beyond the input schema, which has 0% description coverage. However, it does not provide details on parameter formats, constraints, or examples, such as whether database_name can be null or how column_name should be specified. This partial compensation results in an average score.

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 rows with missing values in a table.' It specifies the verb 'Get' and the resource 'rows with missing values,' making it easy to understand. However, it does not explicitly differentiate from sibling tools like 'qlty_missingValues' or 'qlty_columnSummary,' which might offer overlapping functionality, so it misses the top score.

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 lacks context on prerequisites, such as whether the database must be accessible or if specific permissions are needed. Without such information, users may struggle to apply it correctly in real scenarios.

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