Bisque Presentations

Load a presentation into context

get_presentation_context

Read-onlyIdempotent

Load any shared Bisque presentation for reading: its metadata, the full per-slide narration transcript with timestamps, and the context.md file its author shipped for agents (extra background the slides summarize). Target it by watch URL (https://bisque.today/p/{handle}/{slug}) or by handle + slug — it does not have to be yours. Use this to read, summarize, cite, or answer questions about a presentation: ground your answers in the returned transcript and context, and cite slides as [slide N].

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Watch URL, e.g. https://bisque.today/p/{handle}/{slug}. Provide this OR handle + slug.
`slug`	No	URL slug, the last path segment of the watch URL. Use with handle, or pass url instead.
`handle`	No	Channel handle (leading @ allowed).

Output Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes
`title`	Yes
`handle`	Yes
`webUrl`	Yes
`contextMd`	Yes	The bundle's context.md (shared agent-facing background); null when the presentation ships none.
`transcript`	Yes	Per-slide narration, ordered by slide index.
`visibility`	Yes
`description`	No
`publishedAt`	No	ISO 8601, null when unknown.
`presentationId`	Yes
`contextTruncated`	Yes
`transcriptTruncatedSlides`	Yes	Content slides the size-capped transcript dropped; 0 = complete.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 2, 2026

addedInput schema / properties / slug / description

Added value: +"URL slug, the last path segment of the watch URL. Use with handle, or pass url instead."

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond annotations: it works on any shared presentation ('does not have to be yours') and lists the return payload (metadata, transcript, context.md), which is valuable operational detail.

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?

Three sentences, each earning its place: the first defines what is loaded, the second explains targeting, and the third gives usage and citation guidance. No filler or redundancy; the most important information is front-loaded.

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?

An output schema exists, so return values are covered elsewhere. The description supplies the necessary behavioral context (any shared presentation, the citation convention) and covers both targeting methods, making it complete for an agent to call the tool correctly.

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% with all three parameters described. The description restates the url-or-handle+slug alternative, but this is already documented in the url parameter description ('Provide this OR handle + slug'), so the description adds no new semantics beyond the schema.

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 (Load) and resource (shared Bisque presentation) and enumerates exactly what is loaded: metadata, per-slide transcript with timestamps, and context.md. It also clarifies the tool is for reading any shared presentation, distinguishing it from siblings like get_presentation_spec by focusing on the full reading context.

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?

Provides explicit usage direction ('Use this to read, summarize, cite, or answer questions about a presentation') and a concrete citation convention ('cite slides as [slide N]'). It does not name alternative tools to exclude, but the context for when to use it is clear and unambiguous.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Tools are grouped into clear resource families (artifacts, artifact threads, presentations, channels) and descriptions explicitly redirect between create_artifact and create_presentation. The main potential confusion is create_presentation vs publish_narrated_presentation, since both produce presentations but differ in narration source; the descriptions do clarify this.

Naming Consistency5/5

All tools use snake_case verb_noun naming with consistent families like get_artifact, get_artifact_thread, and get_presentation_spec. publish_narrated_presentation is longer but still follows the verb_noun pattern, and there are no mixed casing styles or erratic naming conventions.

Tool Count4/5

19 tools is above the typical 3-15 range, but the count is justified by four clear subdomains: artifacts, artifact threads, presentations, and channels. No tools are redundant, though the set is large enough to feel slightly heavy.

Completeness4/5

Artifacts have full CRUD plus sharing, and threads have create/read/list/reply/resolve. Presentations cover authoring spec, creation/publishing, status, analytics, and reading context, but there is no delete or explicit update endpoint for presentations and no exposed way to fetch mentionables; these are workable gaps rather than fatal ones.

Resources

Need Help?