Skip to main content
Glama

local-mcp

by com.local-mcp
OverviewDiscussionsAdmin

PowerPoint Read

ppt_read
Read-only

Reads slide text content from a PowerPoint presentation (.pptx file).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to the .pptx file
force_downloadNoIf the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of slides
slidesYesPer-slide structured content ({slide, title, bullets[]}), mirroring ppt_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force_download
      Added value: +{
+  "description": "If the file is stored in the cloud and evicted from this Mac (dataless), request the download and wait for it instead of failing. Off by default: a download can take minutes and use metered data, so it is the caller's decision.",
+  "type": "boolean"
+}
  2. Changed4 schema fields changed
    • changedOutput schema / properties / slides / description
      Previous value: -"Per-slide extracted text"New value: +"Per-slide structured content ({slide, title, bullets[]}), mirroring ppt_create"
    • addedOutput schema / properties / slides / items / properties / bullets
      Added value: +{
+  "description": "The slide's body paragraphs, one entry per line",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / slides / items / properties / text
      Removed value: -{
-  "description": "Extracted text content of the slide",
-  "type": "string"
-}
    • addedOutput schema / properties / slides / items / properties / title
      Added value: +{
+  "description": "The slide's title (empty if the slide has none)",
+  "type": "string"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The description is consistent with the readOnlyHint annotation and adds no additional behavioral details such as side effects or permissions. Since the annotation already covers read-only behavior, the description contributes nothing extra, earning a neutral score.

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?

The description is a single concise sentence that opens with the action verb. It is efficient and front-loaded, containing no unnecessary words.

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?

For a simple read operation, the description sufficiently conveys the tool's purpose. It does not specify the output format or whether all slides are included, but given the simplicity of the task, it is reasonably complete.

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?

The tool description does not elaborate on the parameters beyond the schema definitions. Both 'path' and 'force_download' are already well-described in the input schema, so the description adds no extra semantic meaning.

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 it reads slide text from .pptx files, distinguishing it from other file-reading tools. The verb 'Reads' and the resource 'PowerPoint presentation' are specific, leaving no ambiguity about the tool's function.

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

Usage Guidelines3/5

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

The description implies use for extracting text from PowerPoint presentations but does not explicitly contrast with alternatives like ppt_create or other read tools. No explicit conditions or exclusions are given, so guidance is only implied.

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

All local-mcp toolsInspect
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