Skip to main content
Product

Semantic Search and Enrichment

Every tool response is automatically enriched with business context from complementary services. One call replaces four. Bidirectional cross-enrichment is the architectural innovation that separates Plexara from every MCP server that merely wraps an API.

Before and After

What Cross-Enrichment Means Concretely

A single enriched response replaces multiple round trips. The agent receives complete business context without making additional tool calls.

Without Plexara

5+ sequential tool calls

Call 1Describe table schema
Call 2Fetch column descriptions
Call 3Look up data owner
Call 4Check quality scores
Call 5Get deprecation status
ResultAgent assembles context manually

With Plexara

1 enriched response

Call 1Describe table through Plexara
ResultSchema + descriptions + owner + quality + deprecation + glossary terms + lineage

Four Directions

Bidirectional Across Every Service

TrinoDataHub

Query results enriched with catalog metadata: column descriptions, owners, tags, glossary terms, lineage, quality scores, and deprecation warnings.

DataHubTrino

Catalog search results enriched with query engine availability: which datasets are queryable, their resolved table paths, and which Trino connections can reach them.

S3DataHub

Storage objects enriched with catalog metadata: what the object contains, who owns it, its lineage within data pipelines, and any associated quality signals.

DataHubS3

Catalog entities enriched with storage availability: which objects exist in S3, their sizes, last modified dates, and presigned URL access patterns.

Efficiency

Fewer Calls, Better Context

1

Tool call instead of 4+

20pp

Accuracy improvement with semantic context

0

Redundant metadata fetches per session

Enrichment consolidates what would be multiple round trips into single responses. Session-aware deduplication tracks what context has already been provided and avoids repeating it within the same conversation.

Tool visibility filtering hides tools the user is not authorized for, further reducing the number of tool descriptions in the agent context window. Fewer tools means fewer tokens consumed by tool metadata on every request.

The enrichment system uses provider interfaces that decouple enrichment logic from specific implementations. SemanticProvider abstracts the metadata catalog. QueryProvider abstracts the query engine. StorageProvider abstracts object storage.

This abstraction means the enrichment pipeline can evolve its backing services without changing how enrichment works. Replace DataHub with a different catalog, and the enrichment pipeline continues to operate through the same provider interface.

Next

Memory

Persistent knowledge across sessions that makes your AI smarter over time.