Evidence Studio

Get column names and types for the given tables so you can write correct SQL.

get_metadata

Get the raw Markdoc content of a published page. Prefer get_page_summary first.

get_page_content

Get a structured summary of a published page (title, queries, components) so you can describe what it shows.

get_page_summary

Read the raw content of one source file a page references — a partial, a SQL query file, or a custom component — by its path. This is how you follow a `{% partial file="x" /%}` reference or inspect the SQL behind a chart; get_page_content returns pages WITHOUT expanding these. Pass the path as referenced (e.g. "l10/cumulativemaus"). The same path can name both a partial and a query — if so, pass `type` to pick which one. For report pages, use get_page_content.

get_project_file

Get the workspace context (the projects’ agent/context instructions and available skills) that Evidence maintains for AI assistants. Call with no arguments to get context for every project you can access, or pass a projectSlug to scope it to one project. Read this before answering questions about the workspace’s data, metrics, or conventions.

get_context

List the Evidence organizations you belong to. The active organization is fixed to the one you authorized; to act in a different organization, reconnect and select it during sign-in.

list_organizations

List the reusable source files that report pages build on: partials, saved SQL query files, and custom components. Their content lives in separate files that get_page_content does NOT expand — use this to discover them, then get_project_file to read one. For report pages themselves, use list_project_pages.

list_project_files

List the pages within a specific project that you have access to. Use after list_projects.

list_project_pages

List the projects (workspaces) in this organization that you have access to.

list_projects

List the warehouse tables and models available in this workspace. Pass `filter` to narrow using a substring.

list_tables