Skip to main content
Glama

owa_choose_app

Select which running Open Worship app to control when several are open by listing instances by PID, profile, and kind, then setting the active app for subsequent tool calls.

Instructions

Which running Open Worship app to work with, when more than one is running. Without pid, lists them (pid, kind, version, profile, start) and which one is worked with now -- ask the user to pick, by profile and kind, never pick for them. With pid, every tool works in that app from now on (a restart of it is followed). Also says whether this MCP server is the app's version: they should match for the best result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "owa_choose_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
pidNoThe pid of the app to work with, from the list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/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 largely meets it: it discloses that passing `pid` is a persistent, stateful change ('every tool works in that app from now on') and that the selection survives an app restart. It also discloses the listing payload fields and the version-match advisory. It does not say what happens on an invalid or stale pid, or whether the selection persists across sessions, which are the remaining gaps for a stateful tool.

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?

It is a single front-loaded paragraph with no filler sentences; the no-pid case is described before the pid case, matching reading order. It is slightly run-on and relies on dashes and parentheses where separate sentences would read more cleanly, but every clause carries information.

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?

There is no output schema, and the description compensates for the listing case by enumerating returned fields (pid, kind, version, profile, start) plus the current selection. The pid-mode return value is left unspecified, and error conditions are unaddressed, which are the only material omissions for a one-parameter stateful tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `pid` parameter is already documented as 'from the list', so the baseline of 3 applies. The description adds modest value by explaining the consequence of supplying it (persistent targeting, restart-following) rather than restating the type.

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 the specific resource (a running Open Worship app instance) and the operation (choosing which one subsequent tools target), and it distinguishes the two modes: a listing mode without `pid` and a selection mode with `pid`. No sibling appears to do instance selection, so it is distinguishable, though the opening phrase 'Which running Open Worship app to work with' is a fragment that only becomes a verb+resource statement in the following clauses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use ('when more than one is running'), an explicit behavioral rule for the no-argument case ('ask the user to pick, by profile and kind, never pick for them'), and the effect of the argument case. The prohibition against auto-picking is exactly the kind of when-not guidance that prevents agent error.

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