Skip to main content
Glama
Teradata

Teradata MCP Server

Official
by Teradata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Python
Remote

Base Databaselist

base_databaseList
Read-onlyIdempotent

Lists databases or schemas in a Teradata system, with optional filtering for user-created databases only. Use to identify available databases before querying.

Instructions

List all databases or schemas available in the Teradata system. ONLY call when the user explicitly asks which databases or schemas exist on the system. Do NOT call this tool as a preliminary step toward listing tables — if the user asks about tables without naming a database, ask them which database they mean rather than discovering databases first.

Arguments: scope - Filter scope: 'user' returns only user-created databases (excludes system databases), 'all' returns every database. persist - If True, materializes result as a volatile table and returns table name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoFilter scope: 'user' returns only user-created databases (excludes system databases), 'all' returns every database.user
persistNoIf True, materializes result as a volatile table and returns table name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / persist
      Added value: +{
+  "default": false,
+  "description": "If True, materializes result as a volatile table and returns table name",
+  "type": "boolean"
+}
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "user",
+  "description": "Filter scope: 'user' returns only user-created databases (excludes system databases), 'all' returns every database.",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.0
    • removedInput schema / title
      Removed value: -"_dynamic_toolArguments"
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only safety profile is covered. The description aligns with this ('List') and adds the persist behavior (materializing as a volatile table), which is useful context beyond the annotations. However, it doesn't disclose return format or ordering, and the persist detail is already present in the schema, so the added value is moderate.

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 front-loaded with purpose and usage guidance, and the parameter documentation is cleanly separated. It's slightly longer than strictly necessary because the params duplicate the schema, but every sentence earns its place — especially the high-value exclusion guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple, two-parameter tool with no output schema and both params optional. It covers purpose, scope semantics, persist behavior, and precise usage boundaries. Nothing an agent needs to call it correctly is missing.

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 100%, with both scope and persist fully documented in the input schema. The description's Arguments section largely restates what the schema already provides, adding minimal new meaning. Baseline 3 is appropriate when the schema carries the documentation burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('List all databases or schemas available in the Teradata system') that clearly distinguishes it from siblings like base_tableList. The explicit instruction not to use it for table-listing tasks further cements its unique role.

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

Usage Guidelines5/5

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

Provides exemplary when-to-use guidance: 'ONLY call when the user explicitly asks which databases or schemas exist.' It also gives an explicit when-not-to-use rule and instructs the agent to ask the user which database they mean instead of discovering databases first — precise routing with no ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools