Skip to main content
Glama

set_slideshow_type

Assign slideshow types to notebook cells by their index, controlling whether a cell becomes a slide, subslide, fragment, skip, or notes. Remove slideshow type with '-' or null.

Instructions

Set the slideshow type for a specific cell by its index

Args:
    index: The index of the cell to modify
    slideshow_type: The slideshow type to set. Valid values are:
                    "slide" - Start a new slide
                    "subslide" - Start a new subslide
                    "fragment" - Fragment (appear on click)
                    "skip" - Skip cell in slideshow
                    "notes" - Speaker notes
                    "-" or null - Remove slideshow type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes
slideshow_typeNo
Behavior4/5

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

Describes the operation and valid values, but lacks behavioral context like permissions, side effects, or irreversibility. Without annotations, description carries full burden but still adequately covers the action.

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?

Efficient docstring format with clear Args section. No wasted words; every sentence adds value.

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?

Given simple tool with 2 parameters and no output schema, description fully covers purpose, parameters, and valid values. Complete for its complexity.

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

Parameters5/5

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

Schema coverage is 0%, but description explains both parameters: index as cell identifier, slideshow_type with all valid values. Adds significant meaning 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?

States 'set the slideshow type for a specific cell by its index' with clear verb and resource. Lists valid slideshow types, distinguishing it from sibling tools that handle different operations.

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?

Implied usage from the description, but no explicit when-to-use or alternatives. Does not mention when not to use or how it relates to other slideshow-related tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jjsantos01/jupyter-notebook-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server