Skip to main content
Glama

owa_guide_step

Advance, rewind, stop, or jump to a step in the running Open Worship App guide, and optionally perform the current step before moving on.

Instructions

Move a running guide: next, back, stop, goto with a step number, or do -- which performs the current step in the app (the same thing the card's Do it button does) and then moves on. The user can press the same buttons on the card themselves, so read owa_guide_status before assuming where they are.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
actionYes
stepNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that 'do' performs the current step in the app like the card's 'Do it' button and then advances, and warns that the user may act on the card concurrently so state can drift. It does not say what happens at the last step, whether 'stop' is irreversible, or how out-of-range 'goto' values fail.

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?

Front-loaded with the action and tightly written; the parenthetical explaining 'do' is justified clarification rather than filler. Slightly dense as a single run-on sentence, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations mean the description must do more, and it does not cover the 'page' parameter, end-of-guide behavior, or error conditions for invalid goto targets. It is adequate for a small 3-parameter navigation tool but has visible gaps.

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 0%, so the description must compensate. It does well for the enum values (next/back/stop/goto/do) and ties stepNumber to 'goto', but the 'page' parameter is never explained, leaving one of three parameters undocumented in both schema and description.

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?

Opens with a specific verb and resource ('Move a running guide') and then enumerates every action the tool accepts, including the non-obvious 'do' behavior. This clearly separates it from owa_guide_start (start) and owa_guide_status (read position) named in 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?

Explicitly directs the agent to 'read owa_guide_status before assuming where they are,' which is real routing guidance against a specific sibling. It stops short of stating when not to use this tool (e.g., when no guide is running, or use start instead).

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