getdeck

Suggest deck

suggest_deck

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. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`tone`	No	Desired mood. e.g. "minimal", "bold", "warm". Omit if the user did not mention one.
`deck_id`	No	The composition the user picked from a previous call's clarify.options. Skips topic matching.
`purpose`	Yes	The user's topic or goal, in their own words. e.g. "startup pitch deck", "quarterly business review"
`theme_id`	No	The theme the user picked from a previous call's clarify.options. Pass deck_id along with it.
`layout_ids`	No	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.
`slide_count`	No	How many slides. If the user did not say, use the default of 10 rather than asking.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

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"
+}

First observedSep 15, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must cover behavioral aspects. It does disclose that the tool is non-destructive (does not generate files), that it returns a single preview link, and that it asks a clarify question. However, it does not specify any side effects beyond not generating files, nor does it mention authorization/rate limits. Given the absence of annotations, the description partially carries the burden but leaves some gaps.

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 description is quite long and includes many procedural details that could be seen as part of the tool's usage rather than just a description. While it is well-structured with clear sections, it is verbose and could be trimmed without losing essential information. The main purpose is stated early, but the length reduces conciseness.

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?

The tool has 6 parameters, no output schema, and no annotations, which raises the bar for completeness. The description covers the main workflow, the clarify interaction, and the use of get_starter_kit. However, it does not detail what the preview link looks like or if there are any constraints on the number of layout_ids (such as matching slide_count). Still, given the complexity, it is fairly complete.

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 description coverage is 100%, so the schema fully documents each parameter. The description adds operational meaning by explaining that deck_id and theme_id come from prior clarify.options and that layout_ids causes the tool to skip topic matching. This goes beyond the schema's static definitions and helps the agent understand how parameters relate to the tool's stateful workflow.

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?

The description clearly states that the tool composes a deck and returns a preview link without generating files. It gives multiple concrete example requests, including both topic-based and layout-based use cases, and explicitly contrasts with returning individual layout links. This distinguishes it sharply from its siblings like get_layout (fetch a single layout) and get_starter_kit (join layouts into a deck).

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?

The description provides explicit when-to-use scenarios with example phrases, and also says 'ALSO use it' for the layout combining case. It also tells the agent what NOT to do (never answer with list of individual layout links) and gives a step-by-step workflow involving calling get_layout and get_starter_kit. This is exemplary usage guidance.

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

All getdeck tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?