Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata

base_databaseList

Retrieve a complete list of all databases available in your Teradata system to manage and access data resources.

Instructions

Lists all databases in the Teradata System.

Returns: ResponseType: formatted response with query results + metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function that implements the 'base_databaseList' tool. It executes a SQL query to list databases, formats the results, and returns a structured response with metadata.
    def handle_base_databaseList(conn: TeradataConnection, *args, **kwargs):
        """
        Lists all databases in the Teradata System.
    
        Returns:
          ResponseType: formatted response with query results + metadata
        """
        logger.debug(f"Tool: handle_base_databaseList: Args: None")
    
        sql = "select DataBaseName, DECODE(DBKind, 'U', 'User', 'D','DataBase') as DBType, CommentString from dbc.DatabasesV dv where OwnerName <> 'PDCRADM'"
    
        with conn.cursor() as cur:
            rows = cur.execute(sql)
            data = rows_to_json(cur.description, rows.fetchall())
            metadata = {
                "tool_name": "base_databaseList",
                "sql": sql,
                "columns": [
                    {"name": col[0], "type": col[1].__name__ if hasattr(col[1], '__name__') else str(col[1])}
                    for col in cur.description
                ] if cur.description else [],
                "row_count": len(data)
            }
            logger.debug(f"Tool: handle_base_databaseList: 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 mentions the return type ('formatted response with query results + metadata'), which adds some behavioral context, but fails to disclose critical traits such as whether it's read-only, has rate limits, requires authentication, or affects system state, which are essential for a tool interacting with a database system.

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 with two sentences: one stating the purpose and one detailing the return type. It is front-loaded with the main action, though the second sentence could be integrated more smoothly, but overall it avoids 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 the tool's simplicity (0 parameters, no output schema), the description is somewhat complete but lacks depth. It covers the basic purpose and return format, but without annotations or output schema, it misses details on behavioral aspects like safety or performance, which could be important in a database context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter information is needed. The description does not add any parameter semantics, but this is acceptable given the lack of parameters, aligning with the baseline for 0 parameters.

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 action ('Lists') and resource ('all databases in the Teradata System'), providing a specific purpose. However, it does not explicitly differentiate from sibling tools like 'dba_databaseSpace' or 'dba_databaseVersion', which also relate to databases but serve different purposes, so it lacks sibling differentiation.

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 any context, prerequisites, or exclusions, leaving the agent without direction on tool selection among the many database-related siblings.

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