Skip to main content
Glama

owa_drop_files

Drops real files or folders from disk onto a labeled control, such as a slide canvas or Documents list, and reports whether the target accepted the drop.

Instructions

Drop real files or folders from the disk onto a control found by its label -- a picture onto the slide canvas, a song file onto the Documents list, a folder onto Resources. Paths must be absolute and under the repository's test-results folder or the temp folder. The answer says whether the control took the drop (accepted, dropped); check the list it went into before saying it worked.

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": {
      "paths": "<paths>",
      "to": "<to>"
    },
    "name": "owa_drop_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe label on the control to drop them on
pageNoPart of the window URL, e.g. "reader.html"; default the main window.
pathsYesAbsolute paths of the files or folders to drop

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.3/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 load and does so well: it discloses the sandbox constraint that paths must be absolute and under test-results or temp, that the result reports `accepted`/`dropped`, and it explicitly warns the agent to verify the destination list before claiming success. It does not cover failure modes or partial drops though.

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?

Three tight sentences: mechanism, then constraint, then verification advice — front-loaded and free of filler. The verification sentence is the one slightly reactive line, but it earns its place as a correctness guard.

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 mutation tool with no annotations and no output schema, the description supplies the missing safety context (path sandbox) and substitutes for the absent output schema by naming the result fields and the verification step. Error behavior and the `page` parameter remain unaddressed.

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 100%, so the baseline is 3, but the description adds a real constraint absent from the schema — the sandboxed absolute-path requirement — and clarifies that `to` is resolved by label rather than selector. The unused `page` parameter gets no mention.

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 gives a specific verb and resource ("Drop real files or folders from the disk") plus the targeting mechanism ("onto a control found by its label"), and the concrete examples (picture onto slide canvas, song onto Documents list, folder onto Resources) make it unmistakably distinct from click/drag siblings.

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?

Usage is communicated through concrete scenarios that imply when this is the right tool (moving disk files onto list/canvas/container controls), and the path restriction acts as a hard precondition. It stops short of naming any alternative tool or stating when not to use it.

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