Skip to main content
Glama

owa_slide_edit

Edit slide documents by reading, updating, adding, deleting, duplicating, moving, or restyling slides, text boxes, and backgrounds, with unsaved changes kept for user review and undo.

Instructions

Change one of the user's slide documents. file: the document as attached, or its name in Documents. slides reads every slide: its boxes with id, words, position and style, in pixels on a slide of width x height. update-slides changes MANY slides in one call: changes [{slide, items}]; an item with id edits that box (text, fontSize, fontFamily, fontWeight, color, backgroundColor, align left|center|right, valign top|center|bottom, left, top, width, height, rotate, round (corner rounding); remove: true takes it off), one without id adds a text box. add-slides adds new slides in one call: changes [{items}] (slide: where it goes, else at the end), each item a new text box, listed back to front -- a box filling the slide with a backgroundColor and no text is its background. update-slide / add-slide take slide and items for one slide; delete-slide and duplicate-slide slide; move-slide slide and to. set-background puts background (a color, a name from backgroundChoices, or "none") behind slides (numbers; all when left out): kept at once, no Save. Colors #RRGGBB or #RRGGBBAA. Every other change stays UNSAVED (a * beside the name, Ctrl+Z undoes it) for the user to Save; each keeps a backup owa_undo puts back -- say so. Change only what was asked.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fileYes
pageNo
itemsNo
slideNo
actionYes
slidesNo
changesNo
backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: it states that every change except set-background stays UNSAVED with a '*' marker, is undoable via Ctrl+Z, that each change keeps a backup owa_undo can restore, and that set-background is committed immediately with no Save. It also specifies the read output shape (boxes with id, words, position and style, in pixels against width x height) and that `slides` is a read action, which is exactly the kind of context an agent needs before mutating a user's document.

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 purpose statement is front-loaded and the remaining text is organized action-by-action in roughly the schema's enum order, with the critical save/undo caveat reserved for the end. The single dense paragraph is long and heavy on parenthetical nesting, which costs some scannability, but virtually every clause carries information that the schema does not.

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 9-parameter, 9-action mutation tool with no annotations and no output schema, the description covers nearly everything an agent needs: action semantics, nesting of changes/items, coordinate units, color formats, the new-slide back-to-front ordering and the background-box convention. Gaps are minor: the `page` parameter is undocumented, and the per-slide item cap (50) and change cap (100) are left entirely to the schema.

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 description coverage is 0% for 9 parameters, so the description must compensate, and it largely does: it explains `file` (attached document or name in Documents), the `slides` and `changes` structures, item fields including `id` presence/absence semantics, `remove: true`, the `slide` and `to` fields for move, and `background` accepting a color, a `backgroundChoices` name, or "none", plus the #RRGGBB/#RRGGBBAA format. The `page` parameter is never mentioned, and the item list is illustrative rather than exhaustive.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource ("Change one of the user's slide documents") and then enumerates every action value, so an agent knows the tool covers reads (`slides`), edits, adds, deletes, duplicates, moves and backgrounds on a single document. It does not name a sibling to distinguish itself from (e.g. owa_slide_file), so differentiation relies on the action list alone.

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?

Each action value is mapped to its intent, giving an implicit but clear routing table: use `slides` to inspect, `update-slides`/`add-slides` for bulk work in one call, the singular variants for one slide, `set-background` for backgrounds. It also closes with the constraint "Change only what was asked". It stops short of explicit when-not-to-use guidance or naming an alternative tool.

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