# AI on Your Lakehouse: Context Comes in Shapes, Not Queries — Zach Blumenfeld, Neo4j

Source: [AI Engineer](https://www.youtube.com/watch?v=kRkcNOsRyYg)  
Feed7 permalink: https://feed7.dev/p/ai-on-your-lakehouse-context-comes-in-shapes-not-queries-zach-blumenfeld-0r4s9u5  
Published: 2026-07-23T07:00:23.000Z  
Trust: Source Linked (source_linked)

## Why Included

Graph-shaped context can expose relationships and document structure that vector search or Text-to-SQL misses. Treat it as an additional retrieval surface, then benchmark it against your own data.

## Source Summary

The workshop builds graph representations over lakehouse tables and documents, letting an agent inspect metadata, traverse linked document hierarchies, and detect document communities. Tool calls are exposed through **MCP history** in the demonstrated setup.

## Practical Implication

Give data agents several context shapes rather than one universal query path. Use a metadata graph to plan SQL, linked views for document neighborhoods, and **community detection** when thematic grouping helps investigation.

## Agent-Ready Context

The workshop builds graph representations over lakehouse tables and documents, letting an agent inspect metadata, traverse linked document hierarchies, and detect document communities. Tool calls are exposed through **MCP history** in the demonstrated setup.

Give data agents several context shapes rather than one universal query path. Use a metadata graph to plan SQL, linked views for document neighborhoods, and **community detection** when thematic grouping helps investigation.

The workshop reports **no accuracy benchmark** for the demonstrated system. Its structured and unstructured graphs are also unlinked, leaving the agent to join extracted identifiers at runtime unless builders add deterministic connections.

## Context Map

- Layer: context
- Domains: data
- Topics: context-engineering, retrieval, mcp

## Uncertainty

- The workshop reports **no accuracy benchmark** for the demonstrated system. Its structured and unstructured graphs are also unlinked, leaving the agent to join extracted identifiers at runtime unless builders add deterministic connections.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
