tessera.kbates9611.chatgpt.site

build_dashboard_fast

FAST DEFAULT for any request that creates a dashboard or adds two or more blocks. Run an ordered plan of up to 12 existing dashboard operations in one WebMCP call. Tessera first opens and names the blank dashboard, then visibly renders each later operation in order with a short presentation cadence; every operation still validates against its normal schema and appears in activity. Start with create_dashboard when needed, then omit dashboardId so later blocks use the newly active dashboard. Set widths on adjacent blocks to define their split; the first card appears full-width, then cards automatically snap, split, and reclaim space as later cards arrive. The response includes the finished dashboard summary, so do not call inspect_dashboard afterward. A brand-new generated image remains one separate add_generated_illustration_card call so Tessera can audit its pixels; approved built-in illustrations can be included here. MODEL GUIDANCE: Default for creating a dashboard or adding two or more blocks. Follow this contract unless the user explicitly requests a different structure: Build a data-driven editorial dashboard that reads like a newspaper, not a pile of widgets. 1. Establish the thesis. Use the dashboard header for a specific decision-oriented title, a short eyebrow naming scope and period, and one sentence explaining the central takeaway. Write chart titles as findings, not generic labels. 2. Lead with the news. Place three or four decision KPIs together in the first content row (four at width 3 or three at width 4). Put the most important KPI first and give only that KPI, or at most two genuinely urgent KPIs, a brighter semantic accent. Keep the remaining KPI surfaces calmer so emphasis is meaningful. 3. Move from overview to explanation to evidence. After the KPI row, show the broadest comparison or trend, such as the top-performing region and the overall pattern. Next explain the contrast with a focused view of the lowest-performing region, the driver, excep…

Input schema

{
  "type": "object",
  "properties": {
    "operations": {
      "type": "array",
      "description": "Ordered dashboard mutations. Arguments must exactly match the separately registered tool schema for that operation.",
      "minItems": 1,
      "maxItems": 12,
      "items": {
        "type": "object",
        "properties": {
          "toolName": {
            "type": "string",
            "description": "Existing dashboard operation to run",
            "enum": [
              "create_dashboard",
              "update_dashboard",
              "set_dashboard_layout",
              "add_tile_placeholder",
              "add_section_header",
              "add_heading",
              "add_kpi",
              "add_text",
              "add_table",
              "add_bar_chart",
              "add_horizontal_bar_chart",
              "add_grouped_bar_chart",
              "add_line_chart",
              "add_donut_chart",
              "add_gauge_chart",
              "add_scatter_chart",
              "add_treemap_chart",
              "add_heatmap_chart",
              "add_sankey_chart",
              "add_illustration_card",
              "add_saved_illustration_card",
              "update_block",
              "move_block",
              "remove_block"
            ]
          },
          "arguments": {
            "type": "object",
            "description": "Arguments for the selected operation; omit dashboardId after create_dashboard to target the active dashboard",
            "additionalProperties": true
          }
        },
        "required": [
          "toolName",
          "arguments"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "operations"
  ],
  "additionalProperties": false
}