Bisque Presentations

Get an Artifact

get_artifact

Read-onlyIdempotent

Read one Artifact: title, who can open it, the Version viewers see (published_version_id, null while a publication is still being prepared), its URL, and for a markdown document its text (content), so a linked document is read in one call. Pass the art_… id from the end of the link.

Input Schema

Name	Required	Description	Default
`artifact_id`	Yes	The Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_….

Output Schema

Name	Required	Description
`url`	Yes	The viewer page.
`icon`	No
`type`	Yes
`title`	Yes
`content`	Yes	The Markdown source of a markdown Artifact's published Version. null for an html page, a presentation, an Artifact that is not yet published, or a sold one you only view.
`group_id`	No
`created_at`	No
`updated_at`	No
`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.
`discoverability`	Yes
`organization_id`	No
`latest_version_id`	No
`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 changedOct 29, 2026

changedInput schema / properties / artifact_id / description

Previous value: -"The Artifact id (art_…)."New value: +"The Artifact id (art_…): the last part of its link, as in bisque.cloud/documents/art_…, /pages/art_… or /artifacts/art_…."

addedOutput schema / properties / content

Added value: +{
+  "description": "The Markdown source of a markdown Artifact's published Version. null for an html page, a presentation, an Artifact that is not yet published, or a sold one you only view.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "artifact_id",
-  "type",
-  "title",
-  "audience_mode",
-  "discoverability",
-  "published_version_id",
-  "url"
-]New value: +[
+  "artifact_id",
+  "type",
+  "title",
+  "audience_mode",
+  "discoverability",
+  "published_version_id",
+  "url",
+  "content"
+]

Changed1 schema field changedSep 24, 2026

addedOutput schema / properties / icon_image_url

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

AddedSep 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety bar is covered elsewhere. The description adds real behavioral context beyond that: published_version_id is null while a publication is still being prepared, and content is only present for markdown documents. That prevents wrong assumptions about nulls and missing fields.

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?

Two tight sentences, front-loaded with the verb and resource, followed by the returned fields and the id hint. No filler and nothing out of order.

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

Completeness4/5

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

With an output schema present and a single required parameter, the description covers what an agent needs to call it correctly, plus the markdown-only caveat. It adds a bit of return-value detail that the output schema already handles, which is harmless but redundant.

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

Parameters3/5

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

Schema coverage is 100% and the artifact_id parameter is thoroughly documented there, including the art_ prefix and pattern. The description's 'Pass the art_… id from the end of the link' largely restates the schema's own wording, so it adds little beyond the baseline.

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?

States a specific verb and resource ('Read one Artifact') and enumerates exactly what comes back (title, access, published_version_id, URL, markdown content). That is clearly distinguishable from list_artifacts and get_artifact_thread, which the description implicitly excludes by scoping to a single artifact.

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

Usage Guidelines3/5

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

The clause 'so a linked document is read in one call' implies the intended scenario (following an art_… link) and motivates using this instead of a multi-call read. But no sibling tool is named as the alternative, and there is no explicit 'when not to use' guidance, so usage is only implied.

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?