Skip to main content
Glama

owa_goto_page

Switches the main Open Worship App window to a specified page so guides and page-dependent tools can continue after the user changes pages; the congregation-facing projector view stays unchanged.

Instructions

Switch the main app window to one of its pages. The case it exists for: a tool answers "no open page matching" because the user is on a different page of that window. A walkthrough card cannot follow the user across a page change, so switch FIRST, then start the guide on the new page. Tell the user the window is about to change before calling it. The projector is untouched -- what the congregation sees does not change. Pages that are windows of their own are not here and cannot be reached this way.

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": {
      "page": "<page>"
    },
    "name": "owa_goto_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesThe main page to switch the window to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.5/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 disclosure burden and does the important part: it names the side effect (the main window's visible page changes) and explicitly states the projector output is unaffected, which is exactly the kind of blast-radius context annotations would normally supply. It omits failure behavior and whether the prior page's state is preserved, which keeps it short of a 5.

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?

Purpose is front-loaded and every paragraph maps to a distinct concern (scope, trigger, ordering, user warning, blast radius). The quoted error string and the restated projector point add a little redundancy, so it is efficient but not maximally tight.

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 single-parameter, no-annotation, no-output-schema tool, the definition covers trigger, ordering, side effects, and exclusions, which is what an agent needs to call it correctly. It leaves open the behavior on an already-active page or an invalid state, a minor gap given there is no output schema to defer to.

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% with a four-value enum, so the baseline is 3. The description adds real meaning beyond the enum by clarifying that only pages belonging to the main app window qualify, explaining why certain page types are absent from the enum.

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?

States a specific verb and resource ("Switch the main app window to one of its pages") and immediately bounds the scope by excluding pages that are windows of their own. An agent can distinguish this from navigate_page, select_page, and close_page without opening any schema.

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?

Gives an explicit trigger condition (a tool answers "no open page matching" because the user is on a different page), a sequencing rule (switch FIRST, then start the guide), and a negative scope (standalone-window pages cannot be reached this way). It also instructs the agent to warn the user before calling.

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