Skip to main content
Glama

get_carousel

Read-onlyIdempotent

One carousel: its slides (text, image, role), style and status. Use it to pick up a carousel in a new conversation, or after a generate call timed out on your side — slides that finished were saved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "carousel_id": "<carousel_id>"
    },
    "name": "get_carousel"
  }
}

Input Schema

NameRequiredDescriptionDefault
carousel_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
noteNo
topicYes
slidesYes
statusYes
theme_keyNo
created_atYes
theme_nameNo
updated_atYes
carousel_idYes
slides_needing_imagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: a carousel may be partially materialized because only slides that finished were saved. It does not cover error behavior for missing/unauthorized IDs, which keeps it from a 5.

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 short sentences, front-loaded with what is returned, followed by the when-to-use rationale. Nothing is redundant or padded.

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?

An output schema exists, so return-shape explanation is largely optional, and the safety profile is covered by annotations. The remaining hole is parameter semantics for two required, undocumented IDs, which is the only thing an agent might get wrong.

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

Parameters2/5

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

Both parameters (workspace_id, carousel_id) have 0% schema description coverage, so the description carries the full burden and says nothing about them — no note that the carousel must belong to the given workspace or what an invalid ID yields. This is a genuine gap rather than a baseline case.

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

Purpose4/5

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

The description names the resource ('One carousel') and enumerates what is returned ('slides (text, image, role), style and status'), so an agent knows exactly what this fetches. It implicitly contrasts with the generate tools via the timeout remark, though it never names a sibling explicitly.

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 gives two concrete situations to call it: rehydrating a carousel in a new conversation, and recovering after a generate call timed out on the client side. That is concrete context rather than inference, but it stops short of explicit when-not guidance or naming an alternative tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources