Skip to main content
Glama
Sign In

Slidev MCP

by io.github.joelbarmettlerUZH
OverviewDiscussionsAdmin

Browse Themes

browse_themes
Read-only

Show the user a visual theme gallery with preview images.

ONLY call this when the user explicitly asks to SEE or BROWSE themes visually (e.g. "show me the themes", "what do they look like", "let me pick a theme"). This renders an interactive gallery in the user's UI.

To show a filtered subset (e.g. only dark themes), first call list_themes to identify matching themes, then pass their names here.

Do NOT call this to decide which theme to use yourself — use list_themes for that instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
themesNoOptional list of theme names to show (e.g. ['dracula', 'neocarbon', 'vibe']). If omitted, all themes are shown. Use list_themes first to find matching themes, then pass the filtered names here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds the crucial behavioral fact that this renders an interactive gallery in the user's UI, which is a user-visible side effect not captured by the annotations. It does not describe what the call returns or what happens if a theme name is invalid, but with readOnly coverage that gap is minor.

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?

The visual-rendering fact is front-loaded in sentence one, followed by trigger, workflow, and anti-pattern in descending priority. Every sentence carries a distinct instruction with no filler.

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 optional-parameter rendering tool with readOnly annotations and no output schema, the description covers purpose, trigger conditions, the filtering workflow, and the sibling it replaces. An agent has everything needed to call it correctly or route elsewhere.

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 parameter description already states the default-to-all behavior and the list_themes workflow, so the prose largely restates the schema. It adds no new semantics such as error handling for unknown names or ordering of displayed themes, so the baseline 3 applies.

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 and resource ('show a visual theme gallery with preview images') and its output medium (interactive gallery in the user's UI). This is clearly distinguishable from sibling list_themes, which is named explicitly as the non-visual alternative.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('ONLY call this when the user explicitly asks to SEE or BROWSE themes visually'), quotes example user phrasings, spells out a two-step workflow for filtered subsets via list_themes, and gives an explicit do-not ('Do NOT call this to decide which theme to use yourself').

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

All Slidev MCP toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources