Skip to main content
Glama

owa_media_file

Manage Open Worship background media and document files by kind: list, inspect, create, update, rename, delete, or import items, with undoable backups.

Instructions

The user's Background files by kind: pictures, clips, tracks (the Images / Videos / Audios tabs), web pages (Webs), and the Documents folder's files (document: import a PDF, PowerPoint, Word, song or slide file from the disk; list them). list names them (full names, "bg.mp4"); info reads one (a web page's text; a document's words, in order, for a song -- with pictures its pages with no readable words drawn as pictures); rename (to newName, extension kept); delete (to the trash, a copy kept so owa_undo puts it back); import copies the file at path on the disk into the folder, never over an existing one; create / update write a web page from content. Nothing reaches a screen. Nothing is lost: a delete goes to the trash and every change keeps a backup owa_undo puts back. Change only what was asked, then say what changed and that it can be undone.

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>",
      "kind": "<kind>"
    },
    "name": "owa_media_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameNoThe full file name shown
pageNo
pathNoA file on the disk, for import
actionYes
contentNoA web page, for create/update
newNameNo
picturesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that delete goes to the trash with a backup that owa_undo restores, that import never overwrites an existing file, that rename preserves the extension, and that 'nothing reaches a screen' (no UI side effect). Gaps remain around what happens when create targets an existing page, what info returns for image/video/audio kinds, and any error behavior, so it is strong rather than complete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The resource scope is front-loaded, but the body is a single run-on sequence of semicolon-chained clauses dense with parentheticals, which makes the per-action semantics harder to scan than a short list would. Almost every clause carries information, so little is wasted, but the packing costs readability.

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, 7-action mutation tool with no annotations and no output schema, the description covers the important ground: what each action does, what list and info yield, and the reversibility model. Remaining gaps are narrow (the `page` parameter, volume/length of info output, behavior on missing names or existing targets) rather than fundamental.

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 coverage is only 38%, so the description must compensate, and it largely does: it maps every `kind` enum value to its content type, explains that `name` is the full file name ('bg.mp4'), that `path` is a disk file for import, that `newName` keeps the extension, that `content` is the web page body for create/update, and that `pictures` controls how unreadable document pages are rendered. Only `page` is left unexplained in both schema and description.

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 names a concrete resource ('the user's Background files') and enumerates the exact actions available on it: list, info, rename, delete, import, create/update. It also scopes the resource to specific tabs (Images / Videos / Audios / Webs) and the Documents folder, which separates it from the lyric/slide/resource file siblings without naming them. It stops short of explicitly contrasting itself with those sibling tools, which keeps it at 4.

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?

Usage is implied through the action vocabulary: import is tied to 'a PDF, PowerPoint, Word, song or slide file from the disk', and delete is tied to owa_undo recovery. However, there is no explicit 'use this instead of owa_lyric_file / owa_slide_file when...' guidance and no stated prerequisites or failure conditions. The operator instruction ('Change only what was asked, then say what changed') is behavioral policy rather than tool-selection guidance.

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