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), and its URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artifact_id`	Yes	The Artifact id (art_…).

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
`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.

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.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, and the description aligns with them by saying 'Read.' It adds meaningful behavioral context beyond annotations, notably that published_version_id is null while a publication is being prepared.

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?

One tightly written sentence that front-loads the core action and then lists the key returned fields. Every clause earns its place; no filler or repetition.

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 single-parameter read operation with readOnly annotations and an output schema, the description is complete. It conveys what the tool returns, including an edge case (null published_version_id), and no missing information is needed for correct invocation.

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 schema already documents artifact_id with its art_... format. The description does not need to add parameter detail; it only implies that the tool operates on a single artifact.

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 states a specific verb and resource: 'Read one Artifact,' and enumerates the returned fields (title, access, viewed version, URL). This clearly distinguishes it from siblings like list_artifacts, get_artifact_thread, and update_artifact.

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

Usage Guidelines4/5

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

'Read one Artifact' makes the primary use case clear: fetch a single artifact's details by ID. It does not explicitly name alternatives or exclusions, but the context is strong enough that an agent can infer when it applies.

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?