Evidence Studio

Render an Evidence Markdoc snippet to an image — a chart, table, big value, or any mix of components and prose. Provide the full markdown including any ```sql inline query blocks it references. Use existing markdown if available.

visualize

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 column names and types for the given tables so you can write correct SQL.

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

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

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.

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 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 the pages within a specific project that you have access to. Use after list_projects.

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