reloadium.com WebMCP Tools, Schemas & Agent Capabilities

reloadium.com

live Unverified (seed import) AI & Agents 204 tools imperative implementation

Paste a topic, URL, or PDF/TXT/MD — get a multi-episode AI podcast with audio, transcripts, timelines and quizzes. 60+ languages.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 67 · Act 127 · Transact 10 · Score: Not yet scored

Tool inspector

showWhiteboard

act imperative

Show a freeform infinite whiteboard in the chat — sticky notes, boxes/shapes and connectors placed at whatever x/y you choose, for brainstorming, mood-boarding, or a rough sketch where the layout is spatial grouping, not a formal structure. This is NOT the right tool when a more specific card fits better: use showGraph for an actual relationship/dependency network (it lays nodes out for you), showQuadrant for a 2-axis comparison, showZoneGrid for a fixed grid of zones, showTimeline for dated events, or showList for a plain list — those all read better than a whiteboard for their own shape of data. Reach for this specifically when the content doesn't have one of those shapes: loose idea clusters, a rough spatial mockup, a sketch of how pieces sit next to each other. Each item needs a `type`, `x` and `y` (pick your own coordinate space, e.g. roughly -600..600 — items are placed exactly where you put them, nothing auto-arranges). `type: "note"` is a sticky note (give it `text`); `rect`/`ellipse`/`diamond` are shapes (`text` becomes a label inside them, `w`/`h` size them, default ~250x250 if omitted); `text` is a freestanding caption (`text` required); `image` places a real photo (give it `imageUrl` — see below; keeps its real aspect ratio unless you give both `w` and `h`; it has no caption of its own, put a nearby `text` item under/beside it if you want one); `arrow`/`line` are connectors — give them `from`/`to` (other items' `id`s of type note/rect/ellipse/diamond/text — NOT image, which can't be bound to; point an arrow near an image's coordinates instead) to actually connect two items, or omit them for an unattached line at `x`/`y`. `color` is a hex code (e.g. "#ffec99") OR a name defined in `palette` (e.g. "vibe") — pick whichever is more natural for how you're building the board: define `palette` once ({"vibe":"#a7d7f9","note":"#ffec99"}) and reference names from every item's `color` if you want one consistent scheme, or just put hex codes directly on items if th…

Page: /

Input schema

Property	Type	Required	Description
`title`	string	no	—
`background`	string	no	Optional: the board's own canvas color — a hex code (e.g. "#1a1a2e") or a name defined in `palette`. Defaults to white. Pick a dark one for content that calls for it (a moody storyboard, a night scene); items with no `color` of their own automatically get a readable ink against it.
`palette`	object	no	Optional: {name: hexColor} — define a color scheme once (e.g. {"vibe":"#a7d7f9","note":"#ffec99"}) and reference the names from items' `color` (or the top-level `background`) instead of repeating hex codes everywhere. Not required — a hex code directly on `color`/`background` always works too.
`items`	array	yes	1-30 items, each placed at its own x/y — nothing is auto-laid-out.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "title": {
      "type": "string"
    },
    "background": {
      "type": "string",
      "description": "Optional: the board's own canvas color — a hex code (e.g. \"#1a1a2e\") or a name defined in `palette`. Defaults to white. Pick a dark one for content that calls for it (a moody storyboard, a night scene); items with no `color` of their own automatically get a readable ink against it."
    },
    "palette": {
      "type": "object",
      "description": "Optional: {name: hexColor} — define a color scheme once (e.g. {\"vibe\":\"#a7d7f9\",\"note\":\"#ffec99\"}) and reference the names from items' `color` (or the top-level `background`) instead of repeating hex codes everywhere. Not required — a hex code directly on `color`/`background` always works too."
    },
    "items": {
      "type": "array",
      "description": "1-30 items, each placed at its own x/y — nothing is auto-laid-out.",
      "items": {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "note",
              "rect",
              "ellipse",
              "diamond",
              "text",
              "image",
              "arrow",
              "line"
            ]
          },
          "id": {
            "type": "string",
            "description": "Short stable id (e.g. \"idea-1\") so an arrow/line can reference this item as its `from`/`to`. Optional if nothing will connect to it."
          },
          "x": {
            "type": "number"
          },
          "y": {
            "type": "number"
          },
          "w": {
            "type": "number",
            "description": "Width, for rect/ellipse/diamond. Optional."
          },
          "h": {
            "type": "number",
            "description": "Height, for rect/ellipse/diamond. Optional."
          },
          "text": {
            "type": "string",
            "description": "Label text — the note/shape's label, the text element's own text, or an arrow/line's label. Not supported on an image item."
          },
          "color": {
            "type": "string",
            "description": "A hex color (e.g. \"#ffec99\"), or a name defined in the top-level `palette`. Fill for note/rect/ellipse/diamond, ink for text/arrow/line."
          },
          "imageUrl": {
            "type": "string",
            "description": "Required for type \"image\": an id (img_N) of an image generated/edited earlier in THIS conversation (from generateImage, editImage, or findGeneratedImages), an id (attach_N_M) of a photo the USER attached directly to an earlier message (from findAttachedImages), or a real https:// URL (e.g. from getBestImage)."
          },
          "from": {
            "type": "string",
            "description": "For arrow/line only: the `id` of the item it starts at."
          },
          "to": {
            "type": "string",
            "description": "For arrow/line only: the `id` of the item it points to."
          },
          "roughness": {
            "type": "number",
            "description": "Optional, for note/rect/ellipse/diamond/arrow/line (not text/image, which have no drawn stroke to roughen): 0 = clean straight lines (architect), 1 = the default hand-drawn look (artist), 2 = extra sketchy (cartoonist). Omit to keep the default."
          },
          "font": {
            "type": "string",
            "enum": [
              "handdrawn",
              "clean",
              "code"
            ],
            "description": "Optional, wherever this item has text (a note/shape's label, a text element, a labelled connector — not an image, which has no text): \"handdrawn\" is the default hand-drawn font. \"clean\" is a normal sans-serif — pair it with roughness:0 for a UI wireframe that should look like an actual UI, not a sketch of one. \"code\" is monospace, for annotating code. Omit to keep the default."
          }
        },
        "required": [
          "type",
          "x",
          "y"
        ]
      }
    }
  },
  "required": [
    "items"
  ]
}