duckboard-webmcp.alexmnahas.workers.dev

{
  "name": "duckdb_sql",
  "kind": "act",
  "impl": "imperative",
  "description": "Execute DuckDB SQL in this tab's browser-local DuckDB-Wasm database. Use SQL to load, join, transform, aggregate, and sample data before presenting it. The session is stateful until the page reloads, so statements may create, query, update, or drop tables and views across calls.\n\nDATA SOURCES\n- Local files must first be selected or dropped by the user. They are registered under local/*; discover them with SELECT * FROM glob('local/*'). Query them with read_csv, read_json, read_parquet, or supported filename shorthand.\n- SQL may read public HTTPS data supported by DuckDB-Wasm. Browser CORS rules still apply: the remote server must allow this page to fetch the URL.\n- DuckDB-Wasm differs from native DuckDB in extension and filesystem support. Consult the Wasm documentation before relying on a native-only feature.\n\nRESULTS\n- Multi-statement SQL executes every statement and persists its changes; structuredContent contains only the final statement's result.\n- The response includes column names, DuckDB types, and JSON-safe rows in structuredContent.\n- Big integers and exact decimals are returned as strings. Binary values are base64 strings.\n\nFIRST-PARTY DUCKDB DOCUMENTATION\n- DuckDB-Wasm overview: https://duckdb.org/docs/stable/clients/wasm/overview\n- DuckDB-Wasm data ingestion: https://duckdb.org/docs/stable/clients/wasm/data_ingestion\n- DuckDB-Wasm extensions and browser limitations: https://duckdb.org/docs/stable/clients/wasm/extensions\n- SQL statements: https://duckdb.org/docs/stable/sql/statements/overview\n- SELECT syntax: https://duckdb.org/docs/stable/sql/query_syntax/select\n- SQL functions: https://duckdb.org/docs/stable/sql/functions/overview\n- Friendly SQL: https://duckdb.org/docs/stable/sql/dialect/friendly_sql\n- Data formats: https://duckdb.org/docs/stable/data/overview",
  "inputSchema": {
    "type": "object",
    "properties": {
      "sql": {
        "type": "string",
        "minLength": 1,
        "description": "DuckDB SQL to execute."
      }
    },
    "required": [
      "sql"
    ],
    "additionalProperties": false
  }
}

{
  "name": "render_html",
  "kind": "act",
  "impl": "imperative",
  "description": "Replace the full-screen canvas with an HTML data visualization. Favor a visual-first result: let the data dominate, keep explanatory text sparse, establish a clear visual hierarchy, use motion only when it communicates change or flow, adapt to the viewport, and preserve accessible names and reduced-motion behavior. The HTML is mounted inside a fresh opaque-origin iframe that cannot access the host page, storage, DuckDB, local files, or WebMCP tools.\n\nPRELOADED RUNTIME\n- Sigvelo design tokens are already loaded with the clean style and blue color preset.\n- @mcp-b/web-components and @mcp-b/viz-components are already registered. Do not import them again.\n- The sandbox already applies the Sigvelo UI font, text and canvas colors, border-box sizing, zero body margin, and full-viewport minimum sizing. Do not repeat those resets.\n- Prefer semantic custom elements and tokens over recreating controls, cards, metrics, tables, or chart chrome with custom CSS.\n\nSIGVELO CUSTOM ELEMENTS\n- Surfaces and layout: sigvelo-accordion, sigvelo-accordion-item, sigvelo-action-bar, sigvelo-card, sigvelo-carousel, sigvelo-carousel-item, sigvelo-divider, sigvelo-expander, sigvelo-form-section, sigvelo-scroll-area, sigvelo-scroller, sigvelo-splitter, sigvelo-tab, sigvelo-tab-list, sigvelo-tab-panel, sigvelo-toolbar, sigvelo-zoomable-frame.\n- Data display and visualization: sigvelo-avatar, sigvelo-badge, sigvelo-breadcrumb, sigvelo-breadcrumb-item, sigvelo-chart, sigvelo-chart-card, sigvelo-comparison, sigvelo-data-table, sigvelo-date, sigvelo-distribution, sigvelo-icon, sigvelo-meter, sigvelo-metric, sigvelo-metric-card, sigvelo-metric-grid, sigvelo-navicon, sigvelo-number, sigvelo-preview-card, sigvelo-progress, sigvelo-rating, sigvelo-sparkline, sigvelo-viz-legend.\n- Feedback and overlays: sigvelo-alert-dialog, sigvelo-callout, sigvelo-dialog, sigvelo-empty-result, sigvelo-empty-state, sigvelo-popover, sigvelo-spinner, sigvelo-toast, sigvelo-toast-item, sigvelo-tooltip.\n- Inputs and actions: sigvelo-button, sigvelo-button-group, sigvelo-checkbox, sigvelo-checkbox-group, sigvelo-color-input, sigvelo-color-picker, sigvelo-combobox, sigvelo-combobox-item, sigvelo-copy, sigvelo-dropdown, sigvelo-dropdown-item, sigvelo-field, sigvelo-file-input, sigvelo-filter-bar, sigvelo-listbox, sigvelo-listbox-item, sigvelo-number-field, sigvelo-pagination, sigvelo-radio, sigvelo-radio-item, sigvelo-search-list, sigvelo-select, sigvelo-selection-summary, sigvelo-share, sigvelo-slider, sigvelo-switch, sigvelo-text-area, sigvelo-text-field, sigvelo-text-mask, sigvelo-toggle-icon, sigvelo-toggle-tag.\n- Behaviors and utilities: sigvelo-include, sigvelo-infinite-scroller, sigvelo-intersection-observer, sigvelo-mutation-observer, sigvelo-resize-observer, sigvelo-slide-activator, sigvelo-timed-content, sigvelo-transition-group.\n- Attribute-friendly visualization elements include sigvelo-card, sigvelo-metric-grid, sigvelo-sparkline, sigvelo-progress, and sigvelo-badge. For sigvelo-metric, label/format/currency may be attributes, but assign a Number to .value when numeric formatting is desired. Use sigvelo-icon with library=\"system\" for built-in icons.\n- Data-bearing elements require JavaScript property assignment after markup: sigvelo-chart.data, sigvelo-data-table.columns and .rows, sigvelo-distribution.values, and sigvelo-viz-legend.items.\n\nSIGVELO DOCUMENTATION\n- Overall visual design reference: https://design-system.sigvelo.com/\n- Web component API manifest: https://unpkg.com/@mcp-b/web-components@0.2.11/dist/docs/custom-elements.json\n- Visualization component API manifest: https://unpkg.com/@mcp-b/viz-components@0.2.11/dist/docs/custom-elements.json\n- Design-system source and tokens: https://github.com/WebMCP-org/design-system\n\nSTYLING AND LAYOUT\n- The iframe is the entire visualization canvas. Avoid an unnecessary outer card or frame.\n- Use semantic tokens directly, such as --sigvelo-color-surface, --sigvelo-color-text-muted, --sigvelo-color-neutral-border-subtle, --sigvelo-layout-gap, --sigvelo-spacing-*, --sigvelo-radius-*, and --sigvelo-color-viz-series-1 through -6.\n- Do not rename Sigvelo tokens under local variables or add fallback values for preloaded tokens.\n- Write custom CSS only for visualization-specific layout or marks that the components do not provide.\n- Include accessible names for charts, controls, and meaningful graphics. Respect prefers-reduced-motion.\n\nSCRIPTS AND DEPENDENCIES\n- Inline classic scripts, inline module scripts, and HTTPS CDN scripts and styles are supported.\n- Use pinned full esm.sh module URLs, for example import * as d3 from \"https://esm.sh/d3@7.9.0\". Import maps are not supported.\n- Any preview script can transmit rendered data over HTTPS or consume unbounded CPU. The iframe protects the host origin and its capabilities; it is not a network or availability sandbox.\n\nDOCUMENT RULES\n- Prefer a concise HTML fragment containing only the visualization markup and its necessary style and script elements. Complete HTML documents are also accepted.\n- Frames, objects, embeds, base URLs, inline event attributes, and authored document policies are rejected. External scripts and styles must use HTTPS.\n- Each successful call replaces the previous iframe with a fresh realm, so do not rely on globals from an earlier render.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "html": {
        "type": "string",
        "minLength": 1,
        "description": "A concise HTML visualization fragment or complete document."
      }
    },
    "required": [
      "html"
    ],
    "additionalProperties": false
  }
}