Skip to main content
Glama

glass_type

Types text into the focused window as individual keystrokes, triggering autocomplete and validation. Click the target field first to ensure correct focus.

Instructions

Type a string of text into the focused window. Does not focus anything itself — click the field first (glass_click_element, or glass_click), or the text goes wherever focus already was. Sent as individual keystrokes, not a paste, so per-key handlers, autocomplete and validation all run; a newline in text does not press Return, so send that as a separate glass_key. Prefer glass_set_value for a field the a11y tree exposes: it addresses the field directly and reports whether the value landed, where this types wherever the cursor already sits and cannot tell you what it hit. Optional return: "snapshot" settles the UI then folds a fresh a11y tree into the result (and refreshes the snapshot cache); "settle" waits for the UI to stop changing (text-only); omit or "none" for no observe (default).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to type into whatever currently has keyboard focus — this tool does not focus a field, so click or `glass_click_element` one first. Sent as synthetic key events, not pasted, so an app's per-keystroke handlers run.
returnNoOptional observe folded into the result: "snapshot" (wait for the UI to settle, then fold a fresh a11y tree, also refreshing the snapshot cache), "settle" (wait for the UI to stop changing, text-only), or "none" (default). Not accepted inside a `glass_do` `type` action — use a `settle` action or the terminal `then` observe there.
Behavior4/5

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

Annotations already mark this as a write (readOnlyHint=false) but the description goes well beyond: it clarifies the tool does not focus anything itself, is keystroke-based rather than a paste, and that newlines do not trigger Return. The `return` snapshot/settle semantics are also explained. No contradiction with annotations.

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?

Four dense sentences, each carrying distinct information (focus requirement, keystroke behavior, alternative, return semantics). Somewhat long but front-loaded with the core caveat ('does not focus') and nothing is filler.

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

Completeness5/5

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

Covers the focus prerequisite, per-key vs paste semantics, the newline/Return behavior, the preferred alternative glass_set_value, and the full behavior of the optional return parameter including the cache refresh side effect. Complete for a typed-input tool.

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 adds real value: the newline-does-not-press-Return caveat for `text`, and the snapshot-cache-refresh semantics for `return`, which the schema only summarizes. It clarifies behavior beyond the schema's property descriptions.

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?

'Type a string of text into the focused window' states a specific verb, object, and scope in one sentence. It explicitly differentiates itself from glass_set_value, which targets the a11y tree, and glass_key for discrete keys — a model can route correctly without opening the 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?

Exceptionally explicit: it tells the agent to click the field first (naming glass_click_element / glass_click), flags that a newline won't press Return and must be a separate glass_key, and instructs to prefer glass_set_value when the a11y tree exposes the field. Routing decisions are spelled out, not left to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fixed-width/glass'

If you have feedback or need assistance with the MCP directory API, please join our Discord server