Skip to main content
Glama

read_slide_zip

Read specific files or auto-discover text/XML content inside an exported slide ZIP to inspect slide XML, relationships, chart data, and Content_Types beyond standard slide XML.

Instructions

Read multiple files from the exported slide zip. Returns slide XML, relationships, chart XMLs, and Content_Types. Use this to inspect chart data, rels, or other zip contents beyond what read_slide_xml provides. When no paths specified, auto-discovers all text/XML files in the zip.

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": {
      "slide": "<slide>"
    },
    "name": "read_slide_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsNoSpecific zip paths to read (e.g. ["ppt/slides/slide1.xml", "ppt/charts/chart1.xml"]). If omitted, auto-discovers all text/XML files.
slideYesSlide number, 1-based (slide 1 = first slide)
presentationIdNoTarget presentation ID from list_presentations. Optional when only one presentation is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.1
    • addedInput schema / properties / slide
      Added value: +{
      +  "description": "Slide number, 1-based (slide 1 = first slide)",
      +  "maximum": 9007199254740991,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / slideIndex
      Removed value: -{
      -  "description": "Zero-based slide index",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "slideIndex"
      -]New value: +[
      +  "slide"
      +]
  2. First observedv0.6.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the return payload (slide XML, relationships, chart XMLs, Content_Types) and the no-paths auto-discovery default. It does not state that the operation is read-only/non-mutating, nor any size or output-volume caveats when auto-discovering every text/XML file in a deck, which matters for an unbounded read.

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?

Three short sentences, purpose first, alternative second, default behavior last. No filler or repetition; each sentence carries information an agent needs to pick and call the tool.

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?

There is no output schema, so describing the returned contents is essential and is handled well. The remaining gap is behavioral rather than structural: no note on read-only semantics or on the volume/size of output when auto-discovering all zip files, which is the main risk for a tool that can return many files at once.

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 description coverage is 100%, so all three parameters, including the paths example and the 1-based slide note, are already documented in the schema. The description only echoes the auto-discovery default that the schema already states, adding no syntax or constraint detail beyond it. Baseline 3 applies.

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 and resource ('Read multiple files from the exported slide zip') and immediately names the sibling it complements and extends ('beyond what read_slide_xml provides'). An agent can distinguish it from read_slide_xml and edit_slide_zip without opening either schema.

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?

Gives an explicit selection condition against a named alternative: use this for chart data, rels, or other zip contents that read_slide_xml does not cover. It stops short of stating when NOT to use it (e.g., for plain text extraction, where read_deck_text or scan_slide would be cheaper), so the routing is clear but not fully exhaustive given the large sibling set.

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