Skip to main content
Glama

owa_list_questions

Lists supported questions by page and panel, with the recipe and keystroke that answers each. Matches vague or failed searches to the nearest supported questions in the user's own words.

Instructions

The questions this app is prepared to answer, grouped by the page and panel they belong to, each carrying the manual recipe, control and keystroke that answers it. Use it when the user asks what they can ask, when their question is too vague to search for, or when the manual comes back empty -- offer the nearest supported questions in their own words instead of guessing at a feature. query ranks the list against what they said; no query gives the outline.

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

Input Schema

NameRequiredDescriptionDefault
pageNoNarrow to one page of the app.
focusNoThe window they are in; drops other windows' questions.
limitNo
queryNoWhat the user said, in their words. Left out, the result is the section outline rather than individual questions.
sectionNoNarrow to one section id from the outline, e.g. "screens".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description still discloses the shape of the result (questions grouped by page and panel, each with recipe/control/keystroke) and how `query` changes output from ranked questions to a section outline. It never explicitly states this is a side-effect-free read, which is the main residual gap.

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 sentences, front-loaded with what the tool returns before the usage triggers. Dense but every clause carries information; the middle sentence is long yet its three conditions each add routing value.

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 five-parameter, zero-required, annotation-free tool with no output schema, the description effectively substitutes for a return-value spec and explains the query/no-query output modes. Only `limit` and the per-parameter narrowing behavior go unmentioned, which is minor.

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 80%, so most parameters are already documented. The description adds ranking semantics for `query` (it ranks rather than strictly filters) and the outline-vs-questions distinction, but says nothing about `limit`, `section`, or `focus` beyond what the schema already states.

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?

The description names the resource precisely ('the questions this app is prepared to answer'), its organization (grouped by page and panel), and its payload (manual recipe, control, keystroke). That is far more than a restatement of the name and lets an agent distinguish it from a manual/page-lookup sibling at a glance.

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?

Three concrete triggers are given: the user asks what they can ask, the question is too vague to search, or the manual returns empty. It also includes a when-not directive ('offer the nearest supported questions in their own words instead of guessing at a feature'), which is exactly the routing decision an agent needs.

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