Skip to main content
Glama

Bisque Presentations

by cloud.bisque
OverviewDiscussionsAdmin

List your presentations

list_presentations
Read-onlyIdempotent

List the authenticated user's presentations, newest first. One call returns at most limit of them. A non-null nextCursor in the response means more presentations remain: call again with cursor set to that value to get the page after this one, and keep going until nextCursor is null.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of presentations to return per page.
cursorNoThe `nextCursor` from a previous call, to read the page after that one. Omit it to start at the newest presentation.
visibilityNoReturn only presentations with this visibility. Omit to return every one of them.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nextCursorYesPass this back as `cursor` for the next page. Null when this page is the last one.
presentationsYesNewest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "The `nextCursor` from a previous call, to read the page after that one. Omit it to start at the newest presentation.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of presentations to return."New value: +"Maximum number of presentations to return per page."
    • addedOutput schema / properties / nextCursor
      Added value: +{
+  "description": "Pass this back as `cursor` for the next page. Null when this page is the last one.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / required
      Previous value: -[
-  "presentations"
-]New value: +[
+  "presentations",
+  "nextCursor"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of presentations to return."
    • addedInput schema / properties / visibility / description
      Added value: +"Return only presentations with this visibility. Omit to return every one of them."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish this as a safe, read-only, idempotent, closed-world read, so the safety profile is covered. The description usefully adds behavior those annotations cannot express: newest-first ordering, a per-call cap, and the exact continuation/termination rule for pagination.

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, zero filler, and front-loaded with the resource and ordering before the pagination mechanics. Every sentence carries distinct information an agent needs.

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 read-only paginated list with an output schema, the description supplies everything the agent needs: scope, ordering, page size behavior, and the full continuation rule. Return value shape is correctly left to the output schema.

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 goes slightly beyond the schema by tying `limit` and `cursor` together into a loop and stating the termination condition when `nextCursor` is null, which the per-parameter schema text does not spell out.

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 (List), resource (the authenticated user's presentations), and ordering (newest first), which is enough to separate it from siblings like list_artifacts and list_artifact_threads without opening any schema. The scope is explicit rather than tautological.

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?

It clearly describes the calling context for pagination: call again with `cursor` set to `nextCursor`, and repeat until `nextCursor` is null. It does not, however, say when to prefer this over sibling list tools or note any preconditions, so it stops short of full when/when-not 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 toolsInspect
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