apply_template
ChatGPTInstantiate a dashboard from a template. Requires templateId and tableIdMap (array of {sourceTableId, targetTableId} objects). Dimensions with the same name in source and target tables work automatically. For dimensions with DIFFERENT names, you MUST provide dimensionIdMap — use the suggested dimension mappings from get_template. Optional: filterValueMap to override filter values, variableValueMap to override variable values. Optional: dashboardId to inject template pages into an existing dashboard instead of creating a new one. Use get_template with a templateId first to discover source tables, suggested mappings, filters, and variables. For unmapped tables, use list_tables to find candidates and confirm with the user. Review filters and variables with the user before applying — use defaults or ask for overrides based on context.
compare_table_versions
ChatGPTDiff two versions of an Aleph Table. Returns the rows whose value differs (or exists in only one version) across the two versions, with a status column (Added / Removed / Modified). Use list_table_versions first to obtain version IDs — both versions must be on the table's current schema. Output is rendered as a markdown table capped at 50 rows; use filters to narrow the diff if there are more changes than fit. Only applicable to Aleph Tables — does not apply to Integration Tables, Calculated Tables, or Data Warehouse Tables (direct connects).
delete_block
ChatGPTDelete a dashboard block. Pass blockId and pageId. Removes the block from that page's layout; the underlying block remains. Use get_dashboard to find page IDs. IMPORTANT: You MUST show the user the exact changes and get confirmation before calling this tool. [Alpha tool]
delete_calculated_item
ChatGPTDelete a calculated item from a dimension of a table (Aleph or integration). Requires tableId, dimensionName, and itemId. Use get_table for the technical dimension name and canonical tableId, and list_calculated_items to find the itemId. IMPORTANT: this tool is destructive. Always show the user the exact item being deleted and obtain explicit confirmation before calling. [Beta tool]
delete_custom_skill
ChatGPTDelete a custom skill by name. Use list_custom_skills to find skill names.
delete_dashboard_page
ChatGPTDelete a dashboard page. Requires dashboardId and pageId; cannot delete the last remaining page. Use get_dashboard to find page IDs. IMPORTANT: You MUST show the user the exact changes and get confirmation first. [Alpha tool]
delete_mapping
ChatGPTPermanently delete a mapping and all of its rules, detaching it from any transformations that use it. Identify the mapping by its ID (from list_mappings). [Beta tool]
delete_mapping_rules
ChatGPTRemove rules from a mapping by exact when match. Inspect rules with list_mapping_rules first to confirm what you intend to remove. IMPORTANT: Show the user the exact changes and get explicit confirmation before calling. [Beta tool]
export_dashboard
ChatGPTExport a dashboard to PDF and get a downloadable link. Use this when the user wants to export, download, or get a PDF of a dashboard. Returns a public URL to the generated PDF. [Beta tool]
get_ai_settings
ChatGPTGet the workspace's AI settings: the Aleph agent settings and scan settings.
get_block
ChatGPTInspect a single block — returns metadata, and optionally chart configuration or rendered data. Data is queried through the parent dashboard's global filters so it matches what the viewer sees; pass applyParentsGlobalFilters: false to bypass them. Custom data blocks can't be read yet. Use search_blocks to discover blocks, or get_dashboard to inspect page layouts and find block IDs.
get_current_workspace
ChatGPTGet the currently active workspace (also called 'tenant' internally). Use this when the user asks which workspace they are in, or to verify context before destructive operations.
get_custom_skill
ChatGPTGet full details of a custom skill by name, including its content. Use list_custom_skills first to find skill names.
get_dashboard
ChatGPTGet a dashboard with its pages and blocks. Returns dashboard name, description, and for each page: name, description, and list of blocks with their layout positions (name, ID, type, x, y, width, height). Supports lookup by ID or name.
get_dashboard_table_theme
ChatGPTReturns a theme's full style object — same shape as the object branch of manage_block's chartFormat.exploreStyles. Use to customize a named theme: fetch here, mutate locally, pass the whole object to manage_block. The workflow is needed because chartFormat.exploreStyles is a single value written wholesale — there's no partial-merge mode, so sending only the fields you want to change leaves the rest unset rather than inherited from the prior theme. The returned subtotalsStyle array always has 3 entries (matching how custom themes are stored; the workspace UI labels them "Subtotal 1", "Subtotal 2", "Subtotal rows 3+"). The renderer applies entries strictly by index — levels beyond the array length render with no overrides. If the table has more or fewer than 3 subtotal levels, decide based on user intent: replicate the last entry across remaining levels for one consistent look, or trim/leave-unstyled if the user only wants specific levels styled. [Alpha tool]
get_integration
ChatGPTGet basic information about a specific integration (name, ID, status, type, additional context). To view pass-through columns for an integration, call get_pass_through_columns_schema instead.
get_mapping
ChatGPTGet a mapping by ID, including its rules lookup table by default.
get_pass_through_columns_schema
ChatGPTGet the schema for pass-through columns configuration. Returns all source tables with their column names and types, plus the current pass-through column config. Essential for understanding what columns are available to add as custom columns.
get_table
ChatGPTGet detailed information about a specific table. Returns dimensions and measures with importance labels, model type, and overall table importance. Importance levels: high (within 10% of top), medium (≥50%), low (≥10%), negligible (<10%), no data (never queried). Dimension importance reflects how frequently each dimension is queried within this table. Supports lookup by table ID or name.
get_template
ChatGPTGet dashboard template details and instantiation metadata: source tables with suggested target table mappings, dimension mappings, filters, variables, and available tenant tables for unmapped sources. Use this to understand what mappings are needed before calling apply_template.
get_user
ChatGPTGet a single workspace member's details.
get_user_group
ChatGPTGet a user group by ID.
get_user_settings
ChatGPTRead the current user's settings (such as notification preferences). Use this to inspect the current values before changing them with manage_user_settings. [Beta tool]
list_calculated_items
ChatGPTList calculated items on a table — works on both Aleph and integration tables. Each item is returned with itemId, name, dimensionName, human-readable formula, custom/pending flags, and the full formulaAST (needed to round-trip into manage_calculated_item). Use this to: (1) check whether an item already exists before create to avoid duplicate-name errors; (2) discover an itemId for update/delete; (3) audit items where pending: true indicates the formula references values that do not currently resolve; (4) read an item's formulaAST as the starting point for editing via manage_calculated_item. Filters: dimensionName (technical name like "account_type") and custom (true → user-created, false → system/native). When custom is omitted, only custom items are returned. [Beta tool]
list_custom_skills
ChatGPTList all custom skills configured for this workspace. Returns skill names and descriptions. Use get_custom_skill with a skill name to retrieve its full content.
list_dashboard_themes_and_colors
ChatGPTList the workspace's color palettes and table themes. For bar and line chart blocks, pass the name from a chartColors entry into the block's top-level chartColors field (i.e. chartColors: "categorical" or chartColors: "diverging"). Each entry's currentPalette shows the workspace's currently-configured palette name and colors for that kind. For table blocks, pass the name from a tableThemes entry into the block's chartFormat.exploreStyles field (e.g. chartFormat: { exploreStyles: "Automatic" }).Only set these fields when overriding the workspace default; omit them to use the default. The workspace's currently-configured table theme is reported as defaultTableTheme, and the default for line and bar charts is 'categorical'. Other charts can't be customized yet. [Alpha tool]
list_dashboards
ChatGPTList dashboards with name, parent, and block names. Use get_dashboard for full details.
list_data_warehouses
ChatGPTList data warehouse connections the user can query with SQL. Call before run_sql_query to discover available warehouses.
list_integrations
ChatGPTList all data integrations connected to the workspace. Returns integration IDs, names, types, and status information. Use this to discover available integrations for custom column operations.
list_mapping_rules
ChatGPTSearch rules within a mapping. Filter by status (pending/resolved/all), whenEquals (dependent-column values), or thenEquals (output-column values). With no filter, returns pending rules first then resolved up to limit. Always returns total + pending counts so the LLM can decide whether to narrow.
list_mappings
ChatGPTList mappings, sorted with pending ones first.
list_table_versions
ChatGPTList the version history of an Aleph Table — each version represents a push, restore, or other write. Returns up to 200 versions (default 50), newest first, including id, message, submitter, date, latest marker, and source spreadsheet name when applicable. Only versions on the table's current schema are returned (older-schema versions cannot be restored or compared and are not surfaced). Only applicable to Aleph Tables — does not apply to Integration Tables, Calculated Tables, or Data Warehouse Tables (direct connects). Use list_tables or get_table first to find the tableId — Aleph Tables show as Type: Aleph Table. Use this when the user asks about a table's history, recent changes, or who modified data.
list_tables
ChatGPTList all tables available to the user, sorted by importance (most important first). Each table includes an importance label reflecting how frequently it is used by this tenant relative to their most-used table: high (within 10% of top), medium (≥50%), low (≥10%), negligible (<10%), no data (never queried). Prefer higher importance when choosing between similar tables. Dimensions also include importance labels within each table.
list_templates
ChatGPTList all accessible dashboard templates with name, category, and description. Use get_template with a templateId to see full details and instantiation metadata.
list_user_groups
ChatGPTList the user groups in the current workspace.
list_users
ChatGPTList the members of the current workspace. Use this to see who has access to the workspace, or to find a user's ID before calling get_user.
list_workspaces
ChatGPTList all workspaces the current user is a member of (also called 'tenants' internally). Use this to find a workspace ID or domain before calling switch_workspace, or to answer questions about which workspaces the user has access to. Marks the currently active workspace.
manage_ai_settings
ChatGPTUpdate the workspace's AI settings. Pass only the sections you want to change; omitted sections are left untouched. Requires permission to manage AI settings.
manage_block
ChatGPTCreate, update, delete, or copy any block type. Supported types: table (pivot), bar/column chart, line chart, waterfall chart, text (rich text), link (URL bookmark). For create: requires type, name. Optionally provide dashboardId + pageId to place on a dashboard page. Explore blocks (table/bar/line/waterfall) also require tableId. Link blocks require chartConfiguration.url. For update: requires blockId. Modify name, description, data config (rows, columns, measureGroup, filters), display config (formatAsFinancials, dedupeRows, showSubtotals, showRowGrandTotal, showColumnGrandTotal), chart config, text content. For delete: requires blockId and pageId. Removes the block from the specified dashboard page layout only; the underlying block remains available. For copy: requires blockId, dashboardId, pageId (source location), targetDashboardId, and targetPageId (destination). Creates a duplicate of the block and places it on the specified target page. Defaults: name = "Copy of <original>"; width/height = source block's size; x = 0, y = bottom of target page. Override any of name/x/y/width/height to customize placement or sizing. Blocks created without dashboardId + pageId automatically expire after 90 days if not added to a page. Number format presets accepted: Default, Financial, Accounting, Percentage, AccountingThousands, FinancialThousands, AccountingMillions, FinancialMillions. Date format presets accepted: LongDate, ShortDate, MonthOnly, Month, MonthYear. Color presets for conditional formatting: red, lightRed, green, lightGreen, yellow, none. NOT SUPPORTED — Block types: cannot create KPI blocks; cannot create or modify custom data blocks. Operations: cannot change a block's type after creation (e.g., table to bar); cannot move blocks between pages. Config: chart series config (lineIndices, invertedIndices, etc.) requires numeric array indices — row-name-based selection is not supported; measure filters (measureFilters field, separate from dimension filters) are supported but get_block does not yet display them; per-column conditional formatting works but get_block flattens multi-level column headers, making it hard to discover correct column values; per-column widths, partial data range (selectedRange), and AI scan settings (variance thresholds) are not available. IMPORTANT: Always use technical dimension names (e.g. "account_type"), NOT display/pretty names (e.g. "Account Type"). Use get_table to find the correct technical names shown in [brackets]. IMPORTANT: You MUST show the user the exact changes and get confirmation first.
manage_calculated_item
ChatGPTCreate, update, or delete a calculated item on a dimension of a table (Aleph or integration). Items are scoped to a single dimension; formulas combine dimension VALUES (dimension nodes — each carrying a resolved dimensionValue from search_values_in_tables) and references to sibling calculated items (calculatedItemReference nodes — each carrying an itemId from list_calculated_items). Discovery before authoring: (1) get_table to find the technical dimension name and canonical tableId; (2) search_values_in_tables to find exact dimension values; (3) list_calculated_items to find sibling itemIds for references. Inputs by operation: create requires tableId, dimensionName, name, formulaAST (optional: headerName, description, category, enabledByDefault, formatAsPercentage); update requires tableId, dimensionName, itemId plus any fields to change — including targetDimensionName to move (the server fixes up references and may produce pending nodes for values absent on the target); delete requires tableId, dimensionName, itemId. IMPORTANT: this tool is destructive. Always show the user the exact changes — including resolved dimension values and any sibling references — and obtain explicit confirmation before calling. [Beta tool]
manage_custom_skill
ChatGPTCreate, update, or delete a custom skill. For create: requires name (kebab-case, unique), description, and content. For update: requires name, plus description and/or content to change. For delete: requires name. Use list_custom_skills to find skill names.
manage_dashboard
ChatGPTUnified tool for dashboard write operations. Currently supports operation: "update" (create and delete are not yet supported). Update can modify: dashboard name/description, page names/descriptions, block layouts, and global filters. Layout uses an 8-column grid: x (0-7), width (1-8), x+width must not exceed 8. Global filters: use globalFilterUpdates with action "add" (requires dimension, operator, value), "update" (requires filterId, plus fields to change), or "remove" (requires filterId). Use get_dashboard to find page IDs and existing filter IDs. Global filter values that don't exist in the dimension silently match nothing and break the page's blocks, so confirm the values are real before applying. Time dimensions are format-sensitive: year="2024", quarter="2024 Q1", month="Jan-2024", day="2024-01-15". NOT SUPPORTED — Dashboard lifecycle: cannot create, delete, or duplicate dashboards. Pages: use manage_dashboard_page tool to create, delete, duplicate, or rename pages; cannot reorder or move pages between dashboards; cannot manage sections/folders. Access control: cannot manage sharing or user permissions (Editor/Viewer roles); cannot toggle aiChatbotIgnore (flag to exclude a dashboard from MCP results). Config: cannot manage custom variables (page-level dynamic filters); per-block layout settings (hideTitle, autoHeight, showSearchBar) are not available. Advanced: dashboard templates (save as template) and dashboard cache invalidation are not available. Use get_template and apply_template for template instantiation. IMPORTANT: You MUST show the user the exact changes and get confirmation first. Supports lookup by dashboard ID or name.
manage_dashboard_page
ChatGPTManage dashboard pages: create, delete, duplicate, or edit (rename). For create: requires dashboardId; optional name (defaults to "Untitled page"). For delete: requires dashboardId and pageId; cannot delete the last remaining page. For duplicate: requires dashboardId and pageId; optional name (defaults to "<original> (Copy)"). For edit: requires dashboardId and pageId; currently supports renaming via name parameter. Use get_dashboard to find page IDs. IMPORTANT: You MUST show the user the exact changes and get confirmation first.
manage_mapping
ChatGPTCreate or update mappings (lookup tables that translate input column values into output values). Supported operations: create, update. Not yet supported: delete. Create requires a name, dependentColumns, outputColumns, and rules (use [] for a shell). dependentColumns and outputColumns must be disjoint — a column name cannot appear in both. Use tableId to wire the mapping into an integration table's transformation. Set then[col].value to null to leave a rule pending; fill via manage_mapping_rules update. Update renames or edits the description (provide at least one of name, description plus mappingId). Pass description: "" to clear an existing description. [Beta tool]
manage_mapping_rules
ChatGPTEdit rules within a mapping. Operations: update — overwrite then on rules whose when matches an existing rule. Works on both pending and already-filled rules; refuses unknown when so typos surface as errors. addNew — append rules whose when is novel; refuses when collisions (use update to change an existing rule). delete — remove rules by exact when match. Inspect rules with list_mapping_rules first to confirm what you intend to change. IMPORTANT: Show the user the exact changes and get explicit confirmation before calling. [Beta tool]
manage_table
ChatGPTCreate, archive, unarchive, publish, unpublish, edit dimensions, and update metadata on Aleph Tables. Supported operations: create, archive, unarchive, publish, unpublish, editDimensions, update. Create requires prettyName and at least one dimension. Supported dimension types: 'any' (free-form string column(s)), 'time' (calendar dimension), 'list' (column(s) constrained to a fixed allowed-values list). Each type takes a levels array — single-element for a flat (single-level) dimension, multi-element for a multi-level (hierarchical) dimension. Use parentFolderName to place the table in a named folder, or omit for root. Archive moves an existing Aleph Table to the archived tables folder. Unarchive moves an archived table back to root. Publish makes a draft table queryable in dashboards and pulls. Re-publishing a table whose schema has changed since the last publish will delete its existing rows from the data warehouse — show the user the impact and obtain explicit confirmation before passing confirmDataLoss=true. When relaying this to the user, paraphrase in plain non-technical language; do not surface internal API or technical terms like "data warehouse", "server", or "confirmDataLoss". Unpublish flips a table back to draft. Refuses if the table has dependent transformations. EditDimensions applies a single addGroup/updateGroup/removeGroup/addValue/removeValue/editValue action to an existing table. addGroup/updateGroup/removeGroup operate on a column (dimension group) as a whole. addValue/removeValue/editValue operate on one allowed value inside an existing column — today restricted to single-level columns of 'list' or 'any' type (multi-level / hierarchy, 'time', and scenario columns are refused with a clear message). On published tables, addGroup only supports flat 'any' dimensions; 'list', 'time', and multi-level / hierarchical addGroup actions require unpublishing first. Renaming, reordering, or adding/removing levels requires an unpublished table. For flat (single-level) 'any' and 'list' dimensions the prettyName is also the persisted column name, so a rename counts as a level change. For multi-level (hierarchical) and 'time' dimensions, renaming via prettyName alone is metadata-only and works on published tables. Type-only swaps between 'any' and 'list' are supported via the updateGroup action in any table state when levels stay the same. Type changes that involve 'time' (either direction) are refused. For multi-level (hierarchical) 'list' dimensions with existing values, level changes are refused even on draft. 'any'-to-'list' with no allowed values succeeds but returns a warning that pushed non-empty values will reject until values are added — for single-level columns use addValue; for multi-level / hierarchical columns, ask the user to finish value setup in the Aleph UI. Update applies a single rename or move action to an existing table via the updateAction field. Use kind="rename" with prettyName to rename, or kind="move" with parentFolderName (string to move to a named folder, null to clear / move to root). Each call applies one action — issue separate calls to rename and move. [Beta tool]
manage_user_settings
ChatGPTUpdate the current user's settings (such as notification preferences). Provide a partial settings object — the fields you include are deep-merged into the existing settings, so omitted fields are left untouched. Call get_user_settings first to see the current values. [Beta tool]
patch_pass_through_columns
ChatGPTAdd or remove pass-through (custom) columns for an integration. IMPORTANT: Before calling this tool, you MUST show the user the exact changes you plan to make and get their explicit confirmation. Existing columns are preserved by default - only specified additions/removals are applied. Use get_pass_through_columns_schema to discover available columns first.
preview_source_table_data
ChatGPTPreview sample data from an integration source table. Shows the raw source structure and column names (not Aleph-processed data). For noColumns integrations, queries the external API either via the NetSuite SuiteTalk select endpoint (for NetSuite) or via the SuiteQL/API Tester path for other sources; otherwise queries synced data in BigQuery. Useful for identifying columns to add as pass-through columns. Column selection only supported for NetSuite SuiteTalk. Filters supported for all noColumns integrations.
preview_table_push
ChatGPTRequired first step before pushing data to an Aleph Table. Stages the data as a preview the user can review before applying. After calling this, use compare_table_versions (with firstVersionId = parentVersionId and secondVersionId = previewId) to fetch the row-level diff and show it to the user; then call push_table with the previewId once they confirm. Returns the preview ID and the parent version ID. Picking a `mode`: Both modes upsert pushed rows by full dimension combination (matching combos have their measure value updated; new combos are inserted). The difference is what happens to existing rows you did NOT push. - `append`: leaves all other rows untouched. Use when adding or updating specific rows without removing anything else. Safe default. - `overwrite`: also DELETES existing rows that fall inside the slice but aren't in the pushed data. Use when fully replacing a slice — e.g. "restate all of Q4 with these numbers." Destructive; only use when the user explicitly asks to replace a slice. What `overwriteScope` does (overwrite only): overwriteScope only applies to overwrite. It's the lever that controls the delete step; with append there is no delete, so overwriteScope is rejected. overwriteScope lists the dimensions that DEFINE the slice being replaced. Existing rows whose values on those dimensions match the values present in rows are cleared and rewritten. Dimensions you do NOT list are free to vary within the slice (the delete does not constrain them) and any unmapped table dimension is NOT part of the predicate either. Example (from the Connect | Push redesign doc — "Replace a Version for one department"). Table dimensions [version, department, employee]. User says: "Restate the Active Forecast for Engineering with these numbers." - Slice is defined by version and department (the columns the delete should match on — every pushed row carries version=Active Forecast and department=Engineering). - employee is free to vary within the slice → leave it OUT of overwriteScope. - Call with mode: "overwrite", overwriteScope: ["version", "department"]. The pushed employee rows are inserted; any other existing row with version=Active Forecast AND department=Engineering (any employee) is deleted. Other versions and other departments stay untouched. If unsure which mode to use, ask the user, or use append. Overwrite is destructive. Only applicable to Aleph Tables (Type: Aleph Table); discover tableId via list_tables / get_table. Provide rows as objects keyed by column name (the table's dimensions and measures). [Beta tool]
pull_data
ChatGPTRun a no-code Explore — Aleph's pivot-style report — and pull the resulting data as a markdown pivot table. Place dimensions in rows and/or columns, set a measureGroup with one measure, and optionally add dimension filters. Discover tables with list_tables / get_table first, then pass the tableId. Use run_sql_query for raw SQL or multi-measure aggregates; use manage_block with type table to save the result as a reusable dashboard block. [Beta tool]
push_table
ChatGPTApply a preview created via preview_table_push as the new head of an Aleph Table. This is the FINAL step in the push flow: only call after (1) preview_table_push returned a previewId, (2) compare_table_versions was used to show the row-level diff to the user, and (3) the user explicitly confirmed the change. Destructive — moves the table head; never call before the user has reviewed and confirmed the diff. Rejects if the table head moved since the preview was created (call preview_table_push again to refresh). [Beta tool]
restore_table_version
ChatGPTRestore a previous version of an Aleph Table as the new head — creates a new version whose data matches the chosen version. Use list_table_versions first to obtain the version ID; only versions on the table's current schema can be restored. This rewrites the table head, so confirm with the user before invoking. Only applicable to Aleph Tables — does not apply to Integration Tables, Calculated Tables, or Data Warehouse Tables (direct connects). [Beta tool]
run_sql_query
ChatGPTExecute a SQL query against a connected data warehouse. Returns rows as a markdown table. Always call list_data_warehouses first to discover available warehouses, then pass the chosen id.
search_blocks
ChatGPTSearch for blocks across all tables by type and/or query, or narrow to a specific table. Useful for discovering existing blocks, finding examples of specific chart types to use as reference, or listing blocks for a specific table.
search_documentation
ChatGPTSearch Aleph documentation to learn about product features and use cases. Can also be used as a fallback when other Aleph MCP tools can't answer the request.
search_values_in_tables
ChatGPTPerform fuzzy search for dimension values across one or more tables. Use this to find which dimensions contain specific values and discover matching results. Useful for checking data availability (e.g., specific years, accounts, categories). Time dimensions are stored in canonical formats — search using these shapes: year=2024, quarter=2024 Q1, month=Jan-2024, day=2024-01-15. Searching with the wrong format returns empty results, not an error.
submit_mcp_feedback
ChatGPTSubmit feedback about an Aleph MCP tool — this server only, not Linear/Datadog/Slack/GitHub or any other connected MCP. Submit when: - A tool returned wrong, misleading, or incomplete results that hurt the user's outcome (bug). - No Aleph MCP tool exists for what the user asked (feature_request). - A workflow required many steps or workarounds that should be streamlined (workflow_friction). - A tool's interface or parameters were confusing (workflow_friction). One submission per distinct issue per conversation. Skip transient errors (timeouts, rate limits) that resolved on retry.
switch_workspace
ChatGPTSwitch the active workspace (also called 'tenant' internally). Only use when the user explicitly asks to change workspace — otherwise stay in the current one. After switching, announce the new workspace name in your response and confirm before any destructive operation. Use list_workspaces first to discover the target id.
trigger_integration_refresh
ChatGPTTrigger a data refresh for an integration. Use this when the user wants to sync latest data or after configuration changes. The refresh runs in the background.
