MCP tools and provenance
DRE MCP provides tools to discover reviewed reports, execute them, refine saved results and explore allowed tables. The connected agent generates the answer; DRE supplies configured data and provenance. Review the rendered SQL, assumptions and underlying results before relying on the answer.
Available tools
Section titled “Available tools”| Tool | Purpose |
|---|---|
find_reports |
Find exposed reports relevant to a question. |
describe_report |
Inspect a report’s purpose, inputs and context before execution. |
run_report |
Run reviewed report SQL with declared variables; return a bounded preview, provenance and exact outputs. |
refine |
Apply structured filters, sorting or aggregation to saved report rows using DRE’s DuckDB plugin. |
find_tables |
Find allowed tables using their documented context. |
describe_table |
Inspect an exposed table and its columns. |
explore |
Execute a bounded structured query over allowed tables on one connection. |
refresh_context |
Validate and replace the active context after definitions or comments change. |
A useful report workflow is find_reports → describe_report → run_report. Use refine to answer a follow-up from saved rows. For a question requiring new data, inspect allowed tables before exploration.
find_tables supports paging through large exposed schemas with limit, offset and the returned next_offset. It returns at most 25 matches by default, with a maximum limit of 100.
Interpret the result label
Section titled “Interpret the result label”Verified report
Section titled “Verified report”The result comes from an explicitly exposed report’s reviewed SQL. Provenance includes declared variables, time, SQL hashes and exact report output downloads.
The label identifies that execution path. It does not certify the report’s business rules or an agent’s interpretation. A report can contain write SQL; disabling delivery suppresses delivery, not SQL side effects.
Derived from verified result
Section titled “Derived from verified result”The result comes from structured operations over saved, typed report rows. DRE’s DuckDB plugin runs the refinement in an isolated in-memory connection; it makes no new warehouse query. The DuckDB plugin must be installed even if the report originally used another source.
Provenance retains the source run and the transformation operations. Review them to understand which filters, grouping or sorting changed the result.
Exploratory (unverified)
Section titled “Exploratory (unverified)”The result comes from a new structured query over explicitly allowed tables, including documented joins on a single connection. Upstream comments and relationships found in report SQL help choose keys and explain context; they do not verify this new answer.
Review the rendered query and assumptions. Cross-connection joins and arbitrary model-authored SQL are outside the current RC.
Cards, SQL and downloads
Section titled “Cards, SQL and downloads”Compatible MCP Apps hosts can show the result card with its origin label, preview, provenance and downloads. Other clients receive structured results and resource links; test card and download support in your chosen host.
The card’s collapsed Rendered SQL section lets you review compiled report SQL, generated exploration SQL, or local transformation SQL plus the original report SQL for derived results. Display SQL may be secret-masked; hashes identify the exact SQL before masking.
Derived and exploratory CSV/XLSX exports carry origin labels. Workbooks include provenance; CSV exports have a downloadable provenance JSON companion. Retained runs and exports live under .dre-mcp/ and follow the configured retention limits.
See the recorded MCP demo for the three result paths, or return to configuration and scope.