Bisque Presentations

Create an Artifact

create_artifact

Publish an HTML page or a Markdown document as a Bisque Artifact: a persistent, versioned page at a stable URL that people can open, comment on, and that you can update later with update_artifact. Pass the whole document as content. The call waits for the page to be ready and returns its URL. It is private to you unless you pass audience or share_with. A page that should remember what people do on it (a checklist, a poll, a sign-up sheet) declares capabilities ['state.read','state.write'] and, when some paths need different access, state.rules; it then reads and writes JSON documents through window.bisque.state. For a narrated presentation use create_presentation instead.

Input Schema

TableJSON Schema

Name	Required	Description
`icon`	No	An emoji that stands for the page, e.g. 📊. The tab and Home Screen show icon_image, not this.
`type`	No	Default html.
`state`	No	Who may read and write which paths of the page's data, by the minimum role: viewer (can open), contributor (a data grant, separate from editing the page), owner. Absent means: everyone who can open reads, contributors and the owner write. Example poll: [{path:'votes',read:'viewer',write:'owner'},{path:'votes/{self}',write:'viewer'}].
`title`	Yes	A short name, the way a document or app is named.
`listed`	No	Show it in listings (the org library, public discovery) rather than link-only. Default false.
`content`	Yes	The full document. For html: a complete page (styles and scripts inline; it runs in a sandboxed frame with no network). For markdown: the Markdown source.
`audience`	No	Who can open the link. owner: only you. users: the people in share_with. public: anyone with the link.
`icon_image`	No	The page's own icon: the favicon in the browser tab and the icon a phone puts on its Home Screen. A data URL: an SVG (data:image/svg+xml,<svg …>) or a base64 PNG, JPEG, WebP, or GIF, at most 512 KB, cropped to a square. An SVG must be self-contained (no links to other files, fonts, or stylesheets); draw shapes rather than text. Without one the page shows the Bisque icon.
`share_with`	No	People to grant access by email (or uid), with a role. [{ "email": "ana@acme.com", "role": "viewer" }]. viewer opens it; editor can also publish new content. Implies audience "users" when audience is omitted.
`description`	No	One sentence saying what the page is; shown in listings.
`capabilities`	No	What the page may do at run time. state.read and state.write give it JSON documents at window.bisque.state (get, patch, list, subscribe); viewer.identity tells it who is viewing (window.bisque.viewer); events.emit lets it record typed Events. Omit for a page that only shows things.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	The viewer page.
`icon`	No
`type`	Yes
`title`	Yes
`group_id`	No
`created_at`	No
`updated_at`	No
`version_id`	Yes	The Version this call authored.
`artifact_id`	Yes
`description`	No
`audience_mode`	Yes	Who can open it: owner, users, org, or public.
`icon_image_url`	No	The page icon set with icon_image; null for the Bisque icon.
`version_number`	No
`discoverability`	Yes
`organization_id`	No
`latest_version_id`	No
`publication_error`	No
`publication_status`	Yes	ready means the URL serves this content now. queued or processing means it is still being prepared; call get_artifact to check. failed carries publication_error.
`viewer_version_mode`	No
`published_version_id`	Yes	The Version viewers see; null until a publication is ready.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

changedInput schema / properties / icon / description

Previous value: -"An emoji for the tab and listing, e.g. 📊."New value: +"An emoji that stands for the page, e.g. 📊. The tab and Home Screen show icon_image, not this."

addedInput schema / properties / icon_image

Added value: +{
+  "description": "The page's own icon: the favicon in the browser tab and the icon a phone puts on its Home Screen. A data URL: an SVG (data:image/svg+xml,<svg …>) or a base64 PNG, JPEG, WebP, or GIF, at most 512 KB, cropped to a square. An SVG must be self-contained (no links to other files, fonts, or stylesheets); draw shapes rather than text. Without one the page shows the Bisque icon.",
+  "type": "string"
+}

addedOutput schema / properties / icon_image_url

Added value: +{
+  "description": "The page icon set with icon_image; null for the Bisque icon.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedSep 16, 2026

addedInput schema / properties / capabilities

Added value: +{
+  "description": "What the page may do at run time. state.read and state.write give it JSON documents at window.bisque.state (get, patch, list, subscribe); viewer.identity tells it who is viewing (window.bisque.viewer); events.emit lets it record typed Events. Omit for a page that only shows things.",
+  "items": {
+    "enum": [
+      "state.read",
+      "state.write",
+      "events.emit",
+      "viewer.identity"
+    ],
+    "type": "string"
+  },
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / state

Added value: +{
+  "additionalProperties": false,
+  "description": "Who may read and write which paths of the page's data, by the minimum role: viewer (can open), contributor (a data grant, separate from editing the page), owner. Absent means: everyone who can open reads, contributors and the owner write. Example poll: [{path:'votes',read:'viewer',write:'owner'},{path:'votes/{self}',write:'viewer'}].",
+  "properties": {
+    "rules": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "path": {
+            "description": "A slash path the rule covers, and everything below it; '' is the root. A trailing {self} names each person's own document under the prefix.",
+            "type": "string"
+          },
+          "read": {
+            "enum": [
+              "anyone",
+              "viewer",
+              "contributor",
+              "owner"
+            ],
+            "type": "string"
+          },
+          "write": {
+            "enum": [
+              "viewer",
+              "contributor",
+              "owner"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "path"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 4, 2026

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description discloses important runtime behavior: 'The call waits for the page to be ready and returns its URL,' and 'It is private to you unless you pass audience or share_with.' It also explains the state capabilities model and sandboxed execution context, adding substantial behavioral context that annotations alone do not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence earns its place: purpose, behavior, privacy, state capabilities, and sibling routing are each covered without repetition. It front-loads the core purpose and keeps the advanced state discussion until after the basic usage is established.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 11 parameters, nested objects, and an output schema, the description covers the essential behavioral and selection context: synchronous readiness, URL return, privacy defaults, state capabilities, and the alternative presentation tool. The schema already documents individual parameters and defaults, so nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful parameter-level context beyond the schema: 'Pass the whole document as content,' the privacy default for audience/share_with, and the capabilities/state.rules pattern. This elevates it above baseline without needing to re-document every field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Publish an HTML page or a Markdown document as a Bisque Artifact.' It clearly defines the artifact as a persistent, versioned page at a stable URL and explicitly distinguishes itself from create_presentation, so an agent can tell it apart from its closest sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: 'For a narrated presentation use create_presentation instead.' It also names update_artifact as the tool for later updates, which helps an agent choose the right tool over the artifact lifecycle. This is clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Bisque Presentations tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?