Skip to main content
Glama

owa_type

Type text into an app box found by its label, placeholder or current text, and optionally press Enter. Also changes drop-down pickers by naming the choice you want.

Instructions

Type text into a box in the app, found by its label, placeholder or the text already in it -- e.g. the Bible reference box. Set submit to also press Enter. When nothing matches it answers with the closest labels on screen; retry with one of those. "Panel > Box" narrows it to one panel. This is also how a DROP-DOWN is changed: a picker is named by the choice it is on right now (or by its label), and value is the words of the choice you want -- a wrong one answers with the choices there are. It cannot drive a code editor field (those need a real keyboard) -- for those, use a guide step that asks the user to type.

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": {
      "find": "<find>",
      "value": "<value>"
    },
    "name": "owa_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
findYesThe label, placeholder or current text of the box, or a list of candidates to try in order.
pageNoPart of the window URL, e.g. "reader.html"; default the main window.
valueYesThe text to type.
submitNoAlso press Enter after typing.

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 burden and does well: it discloses failure behavior (returns the closest on-screen labels, or the available choices for a picker, and should be retried), the Enter side effect via submit, and a hard capability limit. It omits focus/window prerequisites and whether typed text replaces or appends to existing content, which matters for a mutation 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?

Front-loaded with the core action, then side effects, then failure behavior, then edge cases in descending priority. Dense and largely waste-free, though the drop-down tangents and inline quoting of "Panel > Box" make it run longer than strictly necessary.

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 4-parameter, fully-documented-schema tool with no output schema and no annotations, the definition covers targeting, failure recovery, drop-downs, and limitations. The remaining gaps — replace-vs-append behavior and window/focus preconditions — are the only things an agent could still get wrong.

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%, so baseline is 3; the description earns above that by giving semantics the schema lacks — that `find` matches current text or a picker's current choice, that a list is tried in order, and that "Panel > Box" addresses the panel and URL-scoping parameters. It adds real targeting strategy rather than restating field names.

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 (type text) and resource (a box in the app) and immediately disambiguates the lookup key: label, placeholder, or existing text. It goes further by covering the drop-down case and by excluding code editor fields, so an agent can distinguish it from owa_click or a raw keyboard tool without opening a 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?

Explicit when-to-use coverage: normal text boxes, drop-downs (named by their current choice or label), and narrowed scoping via "Panel > Box". It also states when-not to use it — code editor fields — and names the alternative approach (a guide step asking the user to type), which is a concrete routing decision rather than an implied one.

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