Skip to main content
Glama
fcdmoraes

Teradata MCP Server

by fcdmoraes

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LOGMECHNoAuthentication mechanism (TD2 or LDAP)TD2
MCP_HOSTNoHost for HTTP transportlocalhost
MCP_PORTNoPort for HTTP transport8001
DATABASE_URIYesConnection URI: teradata://user:password@host:1025/database
TD_POOL_SIZENoConnection pool size5
LOGGING_LEVELNoLog level (DEBUG, INFO, WARNING, ERROR)WARNING
MAX_ROW_LIMITNoHard ceiling — callers cannot exceed this50000
MCP_TRANSPORTNoMCP transport (stdio or streamable-http)stdio
TD_MAX_OVERFLOWNoExtra connections allowed above pool size10
TD_POOL_TIMEOUTNoTimeout to acquire a connection (seconds)30
DEFAULT_ROW_LIMITNoDefault row limit for read_query1000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pingA

Testa a conexão com o servidor Teradata.

Executa um SELECT simples e retorna a versão do banco, confirmando que a conexão está ativa e configurada corretamente.

read_queryB

Executa uma consulta SQL no Teradata e retorna os resultados.

list_tablesA

Lista as tabelas e views de um banco de dados Teradata.

table_previewB

Retorna uma amostra das primeiras linhas de uma tabela.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a distinct purpose: listing tables, testing connectivity, executing arbitrary queries, and previewing table data. No overlap or ambiguity.

Naming Consistency4/5

All names use snake_case, but patterns vary: 'ping' is a bare verb, while others combine verb_noun (list_tables, read_query) or noun_verb (table_preview). Minor inconsistency, but still clear.

Tool Count2/5

Only 4 tools for a database server is too few. Essential operations like write, DDL, and transaction control are missing, making the set feel incomplete for the domain.

Completeness3/5

Covers read-only operations (list, query, preview, test), but lacks write operations, schema manipulation, and more advanced query support. Notable gaps for a full database server.

Maintenance

ActivityInactive
ResponsivenessNo issues