Skip to main content
Glama

get_slide_format

Retrieve the authoritative Deckrun slide format specification. Learn all layout tags, Markdown syntax, and rules before writing slides. Returns JSON.

Instructions

Fetch the authoritative Deckrun slide format specification. Call this first to learn all layout tags, Markdown syntax, and rules before writing slides. Returns JSON with layout_tags, surface_syntax, example_markdown, and limits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The _get_slide_format() function that executes the tool logic — fetches live schema from SCHEMA_URL, parses JSON, and returns a formatted summary with slide_separator, layout_tags, two_column, notes, example_markdown, limits, heading_convention, and schema_version. Falls back to cached defaults on error.
    async def _get_slide_format() -> list[types.TextContent]:
        """Fetch the Deckrun slide format schema and return it as text."""
        try:
            resp = requests.get(SCHEMA_URL, timeout=15)
            resp.raise_for_status()
            data = resp.json()
            summary = {
                "slide_separator": data.get("surface_syntax", {}).get("slide_separator", "---"),
                "layout_tags": data.get("surface_syntax", {}).get("layout_tags", []),
                "two_column": data.get("surface_syntax", {}).get("two_column", {}),
                "notes": data.get("surface_syntax", {}).get("notes", ""),
                "example_markdown": data.get("example_markdown", ""),
                "limits": {
                    "max_slides": 10,
                    "max_body_size_kb": 50,
                    "pdf_expiry_days": 90,
                },
                "heading_convention": (
                    "Title slide uses # (H1) for presentation title. "
                    "All other slides use ## (H2) for slide heading."
                ),
                "schema_version": SCHEMA_VERSION,
            }
            return [types.TextContent(type="text", text=json.dumps(summary, indent=2))]
        except Exception as exc:
            fallback = {
                "error": f"Could not fetch live schema ({exc}). Using cached rules.",
                "slide_separator": "---",
                "layout_tags": [
                    "<!-- <title-slide /> --> — first slide: title + subtitle",
                    "<!-- <title-content-slide /> --> — heading + bullets",
                    "<!-- <section-header-slide /> --> — section divider",
                    "<!-- <two-content-slide /> --> — two-column",
                    "<!-- <title-only-slide /> --> — heading only",
                    "<!-- <title-no-footer-slide /> --> — no footer bar",
                    "<!-- <content-with-caption-slide /> --> — image with caption",
                    "<!-- <full-blank-slide /> --> — fully blank",
                    "<!-- <blank-slide /> --> — blank with chrome",
                    "<!-- <footer-only-slide /> --> — footer bar only",
                ],
                "heading_convention": (
                    "# (H1) for title slide title, ## (H2) for all other slide headings."
                ),
                "limits": {"max_slides": 10, "max_body_size_kb": 50},
                "schema_version": SCHEMA_VERSION,
            }
            return [types.TextContent(type="text", text=json.dumps(fallback, indent=2))]
  • The _get_slide_format() function in the HTTP transport variant — identical logic to deckrun_mcp.py, fetches live schema and returns formatted JSON or cached fallback.
    async def _get_slide_format() -> list[types.TextContent]:
        try:
            resp = requests.get(SCHEMA_URL, timeout=15)
            resp.raise_for_status()
            data = resp.json()
            summary = {
                "slide_separator": data.get("surface_syntax", {}).get("slide_separator", "---"),
                "layout_tags": data.get("surface_syntax", {}).get("layout_tags", []),
                "two_column": data.get("surface_syntax", {}).get("two_column", {}),
                "notes": data.get("surface_syntax", {}).get("notes", ""),
                "example_markdown": data.get("example_markdown", ""),
                "limits": {"max_slides": 10, "max_body_size_kb": 50, "pdf_expiry_days": 90},
                "heading_convention": (
                    "Title slide uses # (H1) for presentation title. "
                    "All other slides use ## (H2) for slide heading."
                ),
                "schema_version": SCHEMA_VERSION,
            }
            return [types.TextContent(type="text", text=json.dumps(summary, indent=2))]
        except Exception as exc:
            fallback = {
                "error": f"Could not fetch live schema ({exc}). Using cached rules.",
                "slide_separator": "---",
                "layout_tags": [
                    "<!-- <title-slide /> --> — first slide: title + subtitle",
                    "<!-- <title-content-slide /> --> — heading + bullets",
                    "<!-- <section-header-slide /> --> — section divider",
                    "<!-- <two-content-slide /> --> — two-column",
                    "<!-- <title-only-slide /> --> — heading only",
                    "<!-- <title-no-footer-slide /> --> — no footer bar",
                    "<!-- <content-with-caption-slide /> --> — image with caption",
                    "<!-- <full-blank-slide /> --> — fully blank",
                    "<!-- <blank-slide /> --> — blank with chrome",
                    "<!-- <footer-only-slide /> --> — footer bar only",
                ],
                "heading_convention": "# (H1) for title slide, ## (H2) for all other slides.",
                "limits": {"max_slides": 10, "max_body_size_kb": 50},
                "schema_version": SCHEMA_VERSION,
            }
            return [types.TextContent(type="text", text=json.dumps(fallback, indent=2))]
  • The tool schema/definition: name='get_slide_format', description, and empty inputSchema (no required params). Registered in list_tools().
    return [
        types.Tool(
            name="get_slide_format",
            description=(
                "Fetch the authoritative Deckrun slide format specification. "
                "Call this first to learn all layout tags, Markdown syntax, "
                "and rules before writing slides. Returns JSON with layout_tags, "
                "surface_syntax, example_markdown, and limits."
            ),
            inputSchema={
                "type": "object",
                "properties": {},
                "required": [],
            },
        ),
  • The tool schema/definition in the HTTP variant: types.Tool with name='get_slide_format', description, and empty inputSchema.
    _TOOL_GET_SLIDE_FORMAT = types.Tool(
        name="get_slide_format",
        description=(
            "Fetch the authoritative Deckrun slide format specification. "
            "Call this first to learn all layout tags, Markdown syntax, "
            "and rules before writing slides. Returns JSON with layout_tags, "
            "surface_syntax, example_markdown, and limits."
        ),
        inputSchema={"type": "object", "properties": {}, "required": []},
    )
  • deckrun_mcp.py:273-276 (registration)
    The call_tool() handler dispatches name='get_slide_format' to await _get_slide_format() — this is the registration/dispatch point.
    @app.call_tool()
    async def call_tool(name: str, arguments: dict) -> list[types.TextContent]:
        if name == "get_slide_format":
            return await _get_slide_format()
Behavior3/5

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

No annotations provided, so description must bear full burden. It states the tool returns JSON with specific fields, but does not explicitly declare it as read-only or side-effect-free, nor mention any auth or rate limits. The nature of the tool is apparent, but some behavioral detail is missing.

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, front-loaded with action and purpose. Every sentence provides essential information with no redundancy or waste.

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?

Given no output schema, the description fully specifies the return structure (layout_tags, surface_syntax, example_markdown, limits). This is complete for a simple format-fetching tool with zero parameters.

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?

No parameters exist (0 params, 100% schema coverage). Baseline is 4. The description adds value by listing the return fields (layout_tags, surface_syntax, etc.), which helps the agent interpret the output beyond the empty schema.

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 the tool fetches the authoritative Deckrun slide format specification, with specific verb 'Fetch' and resource 'slide format specification'. It distinguishes from sibling 'generate_slide_deck' by indicating this is a preliminary step.

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?

Explicitly says 'Call this first to learn... before writing slides', providing clear when to use. Does not explicitly state when not to use or mention alternatives aside from the implied sibling tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agenticdecks/deckrun-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server