Skip to main content
Glama

SlideForge

by dev.slideforge

Browse SlideForge's Catalog (Unified Discovery)

browse_catalog
Read-onlyIdempotent

Browse the PowerPoint slide catalog progressively. No args -> form overview (when-to-use, bound fields, variant counts). family= -> variant one-liners. q= -> ranked search. variant=/prior_id= -> example payload. type=schema + family -> a compact family-level variant chooser (not a sendable contract); type=schema + family + variant -> that variant's exact payload contract (JSON Schema, capacity, field mapping, examples). Free. Code path: type=widgets = the add_widget() catalog (name= for its contract + thumbnail); type=helpers = python-pptx helper signatures. type=themes + an uploaded theme_id -> that template's branded FURNITURE layouts (its own cover/agenda/divider/closing slides + fill schemas + previews) — render via create_slide(form=template_layout, theme_id, data={layout, fills}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoSemantic search across all variants; returns ranked form/variant matches with scores.
topNoMax results (with type=themes).
nameNoWidget name (with type=widgets): returns the full contract + worked example + a rendered thumbnail.
typeNoOmit for the form overview (or family=/q= to drill in). schema (+family, optionally +variant=) = schema-first discovery: family only returns a compact variant chooser; family+variant returns that variant's exact machine-readable payload contract (JSON Schema for data, capacity limits, intent-field mapping, examples). widgets = the add_widget() catalog for mode=code (name=<widget> for its contract). helpers = python-pptx helper signatures. themes = list themes (built-in + your saved); Default appears first and can be omitted, or use any returned id as theme_id. brands = your brand kits with versions (theme_id=<slug> renders the default version, <slug>@<n> pins n).
limitNoMax results (with q= or family=).
familyNo
offsetNoPagination offset (with q= or family=).
sourceNoTheme source filter (with type=themes). Default all (built-in + your saved).
variantNo
prior_idNo
theme_idNoWith type=themes: an uploaded theme's id -> its branded furniture layouts + fill schemas (render via create_slide(form=template_layout)).

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish a read-only, idempotent, non-destructive profile, lowering the burden. The description adds useful behavioral texture: ranked search, variant one-liners, example payloads, non-sendable choosers, and the fact that theme results are furniture layouts meant to be rendered via create_slide. No contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but dense and front-loaded with the core browsing behavior, then organizes the many modes with delimiters and arrow syntax. The 'Free.' fragment is slightly ambiguous and the code-path section is packed, but every element mostly earns its place.

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 complex browse tool with no output schema, the description is remarkably complete: it enumerates every major entry path, describes the shape of results for each mode, warns about the non-sendable contract case, and connects theme results to create_slide. An agent has enough to invoke the right mode and interpret what comes back.

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 ist 73%, so description must contribute for family, variant, and prior_id. It does partly: it explains family selects a form, variant/prior_id yield example payloads, and type=schema combinations produce chooser/contract outputs. However, family/variant/prior_id are still only implicitly defined, and some param combinations are left for the agent to infer.

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 ('Browse the PowerPoint slide catalog') and sets it apart from sibling creation/management tools. The description immediately signals this is the discovery/exploration entry point, and the mode list clarifies what 'browse' means in practice.

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?

Provides explicit mode-by-mode usage guidance ('No args -> ...', 'family=<form> -> ...', 'q=<text> -> ...') and calls out when a result is not a sendable contract. It also names the relevant sibling (create_slide) for rendering returned theme layouts, so the agent knows the boundary between exploration and execution.

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

All SlideForge toolsInspect
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.6/5.0
Disambiguation5/5

Each tool maps to a distinct phase or responsibility: browse_catalog for exploration, plan_slide for pre-render planning, create_slide/create_deck for single vs multi-slide generation, upload_asset for asset intake, translate_deck for translation, and manage_account for account/job operations. No two tools appear to do the same thing.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with lowercase and underscores (browse_catalog, create_deck, create_slide, manage_account, plan_slide, translate_deck, upload_asset). This uniform convention makes the set predictable and easy to navigate.

Tool Count5/5

Seven tools provide a well-scoped coverage of the PowerPoint generation workflow—from browsing and planning to creating, asset management, translation, and account control—without unnecessary duplication or bloat.

Completeness5/5

The tool surface covers the full lifecycle: exploration (browse_catalog), planning (plan_slide), single/multi-slide creation (create_slide/create_deck), asset upload/generation (upload_asset), translation (translate_deck), and account/job management including deletion and webhooks (manage_account). No obvious dead ends or missing operations.

Resources