Skip to main content
Glama

Read a deck's editable source

get_deck_source
Read-onlyIdempotent

Read the text of a deck's editable files (deck.mdx, pages/, data/, drawings/…) as published in its live version or an earlier one. Use it to review, quote or summarise a deck's content or to plan an edit; this server has no tool that writes slides, so to change them use start_quick_edit (the person edits in the builder) or the CLI. Unpublished web edits live in the draft, not here — get_deck_sync says if there are any. Read-only. Fails for a version list_versions doesn't show, or one published without its source (a CLI older than 0.5, or --no-source).

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": {
      "deck": "<deck>"
    },
    "name": "get_deck_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckYesThe deck's id (starts with `d`) or its slug, as list_decks returns them; case-insensitive. A deck outside this workspace fails with “No deck …” — call list_decks.
versionNoA version number from list_versions. Omit for the live version.
max_bytesNoText budget across all files, 1,000–400,000 bytes (default 120,000). Files are read in path order; one that no longer fits is still listed, with its size and `truncated: true` but no text — raise this to get it.

Output Schema

NameRequiredDescriptionDefault
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / deck / description
      Previous value: -"The deck's id (d…) or its slug, as list_decks shows them."New value: +"The deck's id (starts with `d`) or its slug, as list_decks returns them; case-insensitive. A deck outside this workspace fails with “No deck …” — call list_decks."
    • changedInput schema / properties / max_bytes / description
      Previous value: -"At most this many bytes of text in all."New value: +"Text budget across all files, 1,000–400,000 bytes (default 120,000). Files are read in path order; one that no longer fits is still listed, with its size and `truncated: true` but no text — raise this to get it."
    • changedInput schema / properties / version / description
      Previous value: -"Default: the live version."New value: +"A version number from list_versions. Omit for the live version."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds substantive behavior: hidden failure modes (a version list_versions doesn't show, or one published without source by a CLI older than 0.5 / --no-source) and the fact that this server has no write tool at all. It does not discuss truncation behavior or response shape in the description, but the schema and output schema cover those.

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?

Front-loaded with purpose in the first sentence, then use/alternatives, then failure conditions. Dense but mostly earned; the third sentence packs draft-state, read-only status, and error cases tightly, which is slightly cluttered but not wasteful.

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?

An output schema exists, so return values need no elaboration. Given that, the description covers everything an agent needs: what files, which version, what alternatives exist for edits, where drafts live, and which conditions cause a failure.

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 parameters are self-documented, but the description still adds meaning to `version` by explaining it refers to either the live version or an earlier one and clarifying the failure condition when that version lacks source. The `deck` and `max_bytes` semantics remain schema-only, so it adds value without fully restating.

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 (read) and resource (a deck's editable files) and enumerates the source paths involved (deck.mdx, pages/, data/, drawings/). It also scopes the operation to a live or earlier version, which cleanly separates it from get_deck and get_deck_stats.

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?

Explicitly names the intended uses (review, quote, summarise, plan an edit) and routes the agent away from it for writes: start_quick_edit or the CLI. It also redirects agents seeking unpublished draft edits to get_deck_sync, giving both when-to-use and when-not-to-use with named alternatives.

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.