Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

PowerPoint Create

ppt_create
Destructive

Creates a PowerPoint presentation (.pptx) at path from an array of slides, each {title, bullets:[…]}. The path must be somewhere Local MCP can write; Desktop/Documents/Downloads may need a one-time Files-and-Folders grant (System Settings → Privacy & Security → Files and Folders). Returns {created, path, slides}.

Input Schema

NameRequiredDescriptionDefault
pathYesOutput path for the .pptx file
slidesYesArray of slide OBJECTS, each with a title and optional bullets
confirmNoIgnored; kept for older clients.

Output Schema

NameRequiredDescriptionDefault
pathYesPath of the created .pptx file
slidesYesNumber of slides created
createdYesTrue when the file was created

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to create"New value: +"Ignored; kept for older clients."
  2. Changed2 schema fields changed
    • changedInput schema / properties / slides / description
      Previous value: -"Array of {title, bullets:[]} slide objects"New value: +"Array of slide OBJECTS, each with a title and optional bullets"
    • addedInput schema / properties / slides / items
      Added value: +{
+  "properties": {
+    "bullets": {
+      "description": "Bullet lines",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Slide title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / slides / description
      Previous value: -"Array of slide OBJECTS, each with a title and optional bullets"New value: +"Array of {title, bullets:[]} slide objects"
    • removedInput schema / properties / slides / items
      Removed value: -{
-  "properties": {
-    "bullets": {
-      "description": "Bullet lines",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "title": {
-      "description": "Slide title",
-      "type": "string"
-    }
-  },
-  "required": [
-    "title"
-  ],
-  "type": "object"
-}
  4. Changed2 schema fields changed
    • changedInput schema / properties / slides / description
      Previous value: -"Array of {title, bullets:[]} slide objects"New value: +"Array of slide OBJECTS, each with a title and optional bullets"
    • addedInput schema / properties / slides / items
      Added value: +{
+  "properties": {
+    "bullets": {
+      "description": "Bullet lines",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Slide title",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title"
+  ],
+  "type": "object"
+}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

It provides critical operational constraints that go far beyond annotations, specifically noting that the path must be locally writable and listing the exact system permission (Files-and-Folders grant) that an agent might need to configure or warn the user about.

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 highly concise, front-loading the core function and then immediately addressing the most crucial operational constraints and the expected return format.

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 that this is a file generation tool that interacts with the local OS, the description is exceptionally complete. It covers input structure, execution environment requirements, and expected output.

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?

Although schema coverage is 100%, the description effectively reinforces the required structure of the complex 'slides' parameter—that it must be an array of objects containing at least 'title' and optionally 'bullets'. This helps the agent understand the required data granularity.

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 is highly specific, using the active verb 'Creates' and the resource 'PowerPoint presentation (.pptx)'. It clearly distinguishes this tool from other file-writing siblings like 'excel_create' or 'word_create'.

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 does not explicitly state when this tool should be used versus alternatives. Its focus is on operational constraints (where the file must be saved) rather than conditional usage.

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