InstaDeck

Design guide

get_design_guide

Read-onlyIdempotent

Retrieves deck-building specifications—workflows, layouts, blocks, motion presets, design rules, fonts, and pitch beats—so you can build or restyle an InstaDeck correctly.

Instructions

How to build an InstaDeck: workflow, layouts with their zones, block types, motion presets, design system rules, fonts, pitch story beats and the design and storytelling principles behind them. Call it before creating or restyling a deck.

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": "get_design_guide"
  }
}

Input Schema

Name	Required	Description	Default
`sections`	No	Sections to return. Default: workflow, layouts, blocks, motion, design, pitch

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Oct 23, 2026

changedInput schema / properties / sections / items / enum

Previous value: -[
-  "workflow",
-  "layouts",
-  "blocks",
-  "motion",
-  "design",
-  "fonts",
-  "pitch",
-  "design_principles",
-  "storytelling_principles",
-  "motion_principles"
-]New value: +[
+  "workflow",
+  "layouts",
+  "blocks",
+  "motion",
+  "design",
+  "fonts",
+  "pitch",
+  "schools",
+  "design_principles",
+  "storytelling_principles",
+  "motion_principles"
+]

First observedv0.1.0Oct 21, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so safety is covered. The description adds the useful sequencing signal that this is a prerequisite reference call, but says nothing about the size/shape of the returned content or whether the guide is static versus deck-dependent.

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?

Two sentences: the first front-loads what the guide contains, the second delivers the invocation rule. No filler and nothing redundant with the annotations.

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?

No output schema exists, so the description must convey what comes back; enumerating sections does that adequately for a documentation tool. A brief note on format or volume would make it fully complete, but an agent has enough to call it correctly with just the default sections.

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 enum is fully self-describing, including the default set. The description's topic list loosely mirrors the enum values but adds no interpretation for ambiguous members such as 'schools' or 'motion_principles', so it neither compensates nor harms.

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 names a specific resource (the InstaDeck design guide) and enumerates its contents — workflow, layouts/zones, block types, motion presets, design system rules, fonts, pitch beats, and principles. That is materially more specific than the title 'Design guide' and lets an agent distinguish this reference tool from action siblings like create_deck or apply_ops.

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

Usage Guidelines4/5

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

'Call it before creating or restyling a deck' gives an explicit trigger condition and ordering constraint. It stops short of naming alternatives (e.g. get_example) or stating when the guide can be skipped, so it is strong but not complete.

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