Skip to main content
Glama

owa_menu

List and click Open Worship App menu bar items by path or unique label to inspect availability and trigger commands such as View > Reload.

Instructions

The app's menu bar (File, Edit, View, Tools, Window, Help). list names every item with its path and isEnabled / isChecked, and marks refused the ones nobody may press for the user (Quit, Relaunch, Developer Tools). click presses item by its path ("View > Reload") or its bare label when that is unique. Reload re-reads the window the user is in.

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_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo"Menu > Item", for click
pageNoPart of the window URL, e.g. "reader.html"; default the main window.
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that `list` returns path plus `isEnabled`/`isChecked`, that certain items (Quit, Relaunch, Developer Tools) are marked `refused` and unpressable, and that Reload re-reads the current window. It stops short of saying what `click` returns or whether a click is reversible.

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, front-loaded with the resource and then the two actions, with no filler. The final sentence about Reload is slightly tangential but still earns its place as behavioral context.

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 3-parameter tool with no output schema and no annotations, the description covers the important ground: what list returns, what click does, and which items are blocked. The main residual gap is the return value of `click` and any permission requirements, but overall it is sufficient to invoke correctly.

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 67%, and the description adds real meaning beyond it by explaining the `item` format with a concrete example ("View > Reload") and the fallback to a bare label when unique. The `page` parameter is left to the schema, and the `action` enum values are only implicitly defined through the list/click prose.

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 specific resource (the app's menu bar, enumerating File/Edit/View/Tools/Window/Help) and two concrete verbs, `list` and `click`, so an agent knows exactly what the tool operates on. It does not explicitly contrast itself with the sibling `owa_click`, which is the main thing keeping it from a 5.

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 rather than stated: `list` names every item with path and state, and `click` presses by path or unique bare label, which suggests a list-then-click workflow. It also warns that some items are `refused` and cannot be pressed, but it never says when to prefer this over `owa_click` or what to do when a label is ambiguous.

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