Skip to main content
Glama

owa_slide_file

Create, inspect, edit, rename, revert, or delete slide documents and manage individual slides and text boxes, with all edits kept unsaved and backed up for undo.

Instructions

Look at and change the user's slide documents. list names what is there, info reads one, create makes a new one, update changes one, rename renames one, revert drops its unsaved edits (the editor's Discard, undoable here), delete moves one to the trash. content (for create/update) is the whole document JSON with an items array of slides. One slide at a time is cheaper: slides reads them with their text boxes and style; add-slide adds one (at slide, else last); update-slide changes slide slide -- an item with id edits that box (remove deletes it), one without adds a text box; delete-slide, duplicate-slide, move-slide (to to). Pixels; colors #RRGGBB or #RRGGBBAA. Nothing is lost: delete goes to the trash, create refuses a taken name, update -- like every edit -- stays UNSAVED (a * beside the name, Ctrl+Z undoes it) for the user to Save, and every change keeps a backup owa_undo puts back -- say so afterwards. Ask before changing what they did not ask about.

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": {
      "action": "<action>"
    },
    "name": "owa_slide_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoWhere move-slide puts it, counting from 1
nameNoThe name as it reads in the list, with no folder and no file extension. Not needed for `list`.
pageNo
itemsNoText boxes, for add-slide and update-slide
slideNoWhich slide, counting from 1
actionYesWhat to do
contentNoRequired by `create` and `update`
newNameNoThe new name, for `rename` only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.5/5.0
Behavior5/5

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

There are no annotations, so the description carries the whole load, and it does: delete goes to the trash rather than being permanent, create refuses a name that is already taken, updates remain UNSAVED with an asterisk and are undoable with Ctrl+Z, and every change keeps a backup that owa_undo can restore. It even instructs the agent to tell the user afterwards, which is behavior an agent could not infer from the schema.

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?

The action list is front-loaded, then content, then slide-level operations, then units, then the safety guarantees, so the ordering follows how an agent reads. It is dense and pushes toward the long side, but almost every clause carries information rather than restating the tool name.

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 an 8-parameter, no-annotation, no-output-schema tool, this covers the hard parts: mutation safety, undo path, name collisions, and document versus slide granularity. The gaps are the undocumented page parameter and the absence of any hint about what list or info return, though the lack of an output schema makes the return-format gap less severe.

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?

Coverage is 88%, so the schema already does most of the work, but the description adds meaning: content is the full document JSON with an items array of slides, an item with an id edits that box while remove deletes it, an item without an id adds a text box, and to/slide are 1-based positions. Units (pixels) and color formats (#RRGGBB or #RRGGBBAA) are also clarified. The page parameter remains completely unexplained, which keeps this from a 5.

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?

It states a concrete resource (the user's slide documents) and then enumerates all thirteen actions with a specific verb each: list names, info reads, create makes, revert drops unsaved edits. An agent can tell a document-level action from a slide-level one (slides, add-slide, update-slide, delete-slide, duplicate-slide, move-slide) without opening the 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?

It gives real routing guidance: 'One slide at a time is cheaper' steers toward the slide actions over whole-document content edits, and the closing line asks the agent to confirm before changing anything the user didn't request. The main omission is that it never explicitly points to a sibling such as owa_slide_edit or owa_undo as the alternative path.

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