Skip to main content
Glama

Suggest deck

suggest_deck
Read-onlyIdempotent

Compose a deck and return a preview link the user can open in the browser right away. The user sees what the finished deck looks like without a single file being generated. Use this for requests like "make me a pitch deck", "I need a sales deck", "10 slides for an investor update", "put together a product overview", or "show me a deck outline" - anything where the user has a topic but has not picked layouts yet. ALSO use it when the user already has layouts in hand - "이 레이아웃들 모아서 프리뷰 만들어줘", "combine these layouts into a preview", "추천 프리뷰 만들어줘", "show these together as a deck" - pass them as layout_ids and it returns ONE deck preview link for the whole set. Never answer that kind of request with a list of individual layout links: one deck preview is the deliverable. Returns one theme + a slide order + the preview link, plus a clarify question to put to the user so the composition and theme are their call, not a guess. If order_issues is present in the result, the slide order breaks a rule (closing layout not last, same layout twice in a row): fix it before showing the deck. Always pass the preview link through to the user verbatim, ask clarify.question with its options, and wait for the answer - then call this tool again with deck_id / theme_id as clarify.answer_with says. Do not start generating files while a clarify question is unanswered. Once it is settled, fetch each layout id with get_layout, then call get_starter_kit to join them into one deck.

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": {
      "purpose": "<purpose>"
    },
    "name": "suggest_deck"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoDesired mood. e.g. "minimal", "bold", "warm". Omit if the user did not mention one.
deck_idNoThe composition the user picked from a previous call's clarify.options. Skips topic matching.
purposeYesThe user's topic or goal, in their own words. e.g. "startup pitch deck", "quarterly business review"
theme_idNoThe theme the user picked from a previous call's clarify.options. Pass deck_id along with it.
layout_idsNoLayout ids the user or you already picked, in slide order. Skips topic matching and slide_count: the preview link is built from exactly these layouts.
slide_countNoHow many slides. If the user did not say, use the default of 10 rather than asking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / layout_ids
      Added value: +{
      +  "description": "Layout ids the user or you already picked, in slide order. Skips topic matching and slide_count: the preview link is built from exactly these layouts.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description is consistent with them ('without a single file being generated'). Beyond the annotations it discloses the return shape (one theme, a slide order, the preview link, plus a `clarify` question) and an order_issues condition that must be fixed before showing the deck. The remaining gap is the clarify/answer loop's exact semantics, which are referenced but only partly spelled out.

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

Conciseness3/5

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

The purpose and the primary mode are front-loaded, which is good, but the middle is a dense run-on mixing examples, Korean trigger phrases, the clarify loop, order_issues handling, and the get_layout/get_starter_kit hand-off. Several sentences restate the same rule ('Never answer ... with a list of individual layout links' / 'one deck preview is the deliverable'), so it is longer than it needs to be.

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 6-parameter tool with no output schema, the description covers what an agent needs: what it returns, the clarify question to relay verbatim, the order_issues failure mode, and the required next steps (get_layout then get_starter_kit). Nothing essential to calling it correctly is missing.

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, but the description adds real meaning: layout_ids skips topic matching and slide_count and produces one preview for the whole set, and deck_id/theme_id are the values returned in a prior call's clarify.options and should be re-sent per clarify.answer_with. That is workflow-level semantics the schema alone does not convey.

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?

Opens with a specific verb and resource: 'Compose a deck and return a preview link the user can open in the browser right away.' It also immediately distinguishes itself from file-producing siblings ('without a single file being generated') and names the follow-on tools get_layout and get_starter_kit, so an agent knows where this tool sits in the pipeline.

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 concrete trigger phrases ('make me a pitch deck', '10 slides for an investor update') plus a second, explicitly flagged mode for when layouts already exist ('combine these layouts into a preview' -> pass layout_ids). It also states a negative rule: never answer with a list of individual layout links, since one deck preview is the deliverable. That is explicit when/when-not guidance with alternatives named.

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