Skip to main content
Glama

owa_guide_status

Report the current step, its text, whether the named control was found, nearby labels to use on a miss, and the user's last action in a running guide.

Instructions

Where the user is in a running guide: step number, its text, whether the control this step names was found on screen, the closest labels that ARE on screen when it was not (nearMisses -- restart the guide with one of those), and what they last did (next, back, user-did-it when they clicked the ringed control, closed-by-user).

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

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

B3.4/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 substantial work: it discloses the returned fields and, crucially, the semantics of each last-action value ('next', 'back', 'user-did-it', 'closed-by-user') and the remediation path for nearMisses. What is missing is any statement about the no-guide-running case or whether the call has side effects.

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?

A single, front-loaded sentence that leads with the core question ('Where the user is in a running guide') before enumerating payload fields. The parenthetical explanations earn their place by defining nearMisses and the action enum, though the sentence is dense and slightly convoluted.

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?

Because there is no output schema, the description must explain return values, and it does so thoroughly for a status tool. However, it is incomplete regarding its only input parameter and silent on the no-active-guide case, which matters for an agent polling status.

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

Parameters2/5

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

There is one parameter, 'page', with 0% schema description coverage, and the description never mentions it at all. An agent cannot tell whether 'page' scopes the status lookup, is an optional filter, or is required in practice, so the description fails to compensate for the coverage gap.

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 and scope: 'Where the user is in a running guide', then enumerates exactly what is reported (step number, step text, control-found flag, nearMisses, last action). It is clearly a status/read query, distinguishable in intent from guide-advancing siblings like owa_guide_step, though no sibling is named explicitly.

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 only implied: an agent must infer this is for inspecting a running guide's progress and for diagnosing a failed step, since the description says 'restart the guide with one of those' nearMisses. It never states when to call this versus owa_guide_start or owa_guide_step, nor what happens if no guide is running.

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