mcp-data-platform-v0.19.0

What's New in v0.19.0

Upgrades both core toolkit dependencies and introduces config-driven tool description overrides — deployers can now customize what AI agents see for each tool's description directly in YAML config, without code changes.

Improved Default Tool Descriptions

Both upstream toolkits ship significantly better default descriptions that tell agents not just what a tool does but when to use it:

• trino_query — Now includes catalog.schema.table path format guidance, LIMIT awareness, WHERE clause advice for large tables, and a nudge toward trino_explain for expensive queries
• trino_explain — Now provides concrete triggers: large tables (millions of rows), filter verification, slow query debugging, and join strategy analysis
• trino_describe_table — Highlights include_sample=true for understanding data formats, positions it as the richest single-call for table structure
• All 12 DataHub tools — Enhanced with decision context and cross-references to related tools

These improvements apply automatically with no configuration changes.

Config-Driven Description Overrides

When tools are composed into the platform, semantic enrichment middleware adds capabilities that standalone toolkits can't describe themselves. For example, trino_describe_table returns DataHub metadata (owners, tags, glossary terms, quality scores) via cross-injection — but the upstream description has no knowledge of this.

Deployers can now override any tool's description in platform.yaml:

toolkits:
  trino:
    config:
      descriptions:
        trino_describe_table: "Get table schema with DataHub context — the richest single-call way to understand a table"
        trino_query: "Execute SQL with automatic column-level semantic enrichment from DataHub"
  datahub:
    config:
      descriptions:
        datahub_search: "Search the data catalog for datasets, dashboards, and pipelines"
        datahub_get_entity: "Get full metadata for a catalog entity including query availability"

When descriptions is absent or empty, the improved upstream defaults are used automatically. This is fully backward-compatible.

Dependency Upgrades

Package	From	To
github.com/txn2/mcp-trino	v0.3.0	v0.4.0
github.com/txn2/mcp-datahub	v0.5.2	v0.6.0

Documentation

• Configuration reference updated with descriptions option for both Trino and DataHub toolkit tables
• Example config (configs/platform.yaml) includes commented description examples
• LLM-readable docs (docs/llms-full.txt) updated

Related

Partially addresses #100 (platform-level tool description overrides).

Upgrading from v0.18.x

No breaking changes. Run go get github.com/txn2/mcp-data-platform@v0.19.0 or pull the new Docker image. All existing configurations work without modification — you get improved tool descriptions automatically.

Optional: Add descriptions to your toolkit config blocks to customize tool descriptions for your deployment's specific enrichment setup.

Changelog

Features

• feat: upgrade mcp-trino v0.4.0 / mcp-datahub v0.6.0 with description overrides (#101)

Installation

Homebrew (macOS)

brew install txn2/tap/mcp-data-platform

Claude Code CLI

claude mcp add mcp-data-platform -- mcp-data-platform

Docker

docker pull ghcr.io/txn2/mcp-data-platform:v0.19.0

Verification

All release artifacts are signed with Cosign. Verify with:

cosign verify-blob --bundle mcp-data-platform_0.19.0_linux_amd64.tar.gz.sigstore.json \
  mcp-data-platform_0.19.0_linux_amd64.tar.gz