Skip to main content
Glama
fixed-width

glass

by fixed-width
OverviewSchemaRelated ServersScoreDiscussions
Rust

glass_type

Types text into whatever currently has keyboard focus, as individual keystrokes to trigger autocomplete and validation. Click the target field first; send Enter separately.

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). If at least two next actions or waits are known, use glass_do instead of separate calls.

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.
returnNoTerminal observation: "snapshot" settles and refreshes/folds a11y, "settle" waits for visual stability and returns text-only metadata, and "none" skips observation (default).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / return / description
      Previous value: -"Optional observe folded into the result: \"snapshot\" (wait for the UI to settle, then\nfold a fresh a11y tree, also refreshing the snapshot cache), \"settle\" (wait for the UI\nto stop changing, text-only), or \"none\" (default). Not accepted inside a `glass_do`\n`type` action — use a `settle` action or the terminal `then` observe there."New value: +"Terminal observation: \"snapshot\" settles and refreshes/folds a11y, \"settle\" waits for\nvisual stability and returns text-only metadata, and \"none\" skips observation (default)."
  2. Changed3 schema fields changedv1.2.0
    • addedInput schema / properties / return
      Added value: +{
+  "description": "Optional observe folded into the result: \"snapshot\" (wait for the UI to settle, then\nfold a fresh a11y tree, also refreshing the snapshot cache), \"settle\" (wait for the UI\nto stop changing, text-only), or \"none\" (default). Not accepted inside a `glass_do`\n`type` action — use a `settle` action or the terminal `then` observe there.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / text / description
      Added value: +"Text to type into whatever currently has keyboard focus — this tool does not\nfocus a field, so click or `glass_click_element` one first. Sent as synthetic\nkey events, not pasted, so an app's per-keystroke handlers run."
    • removedInput schema / title
      Removed value: -"TypeArgs"
  3. Addedv1.0.3
  4. Removedv1.0.2
  5. First observedv1.0.1

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: keystrokes are sent individually, not pasted, so per-key handlers run; newline does not press Return; the tool cannot report where text landed; and return modes ('snapshot', 'settle') are explained. Annotations provide no such detail, so the description carries the full burden and does so thoroughly.

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?

The description is dense but well-structured: main action first, then focus caveat, keystroke behavior, alternative tool, and return options. Every sentence adds information, though it is longer than strictly necessary and could benefit from bullet-style segmentation for faster parsing.

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?

Given the tool's interaction complexity—focus dependence, keystroke behavior, return modes, and sibling alternatives—the description covers all essential aspects. It explains prerequisites, side effects, limitations, and fallback tools. No output schema exists, but the return modes are clearly described, making it complete for an agent to invoke correctly.

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% and both parameters already have descriptions. The tool description adds value by clarifying the practical implications of 'text' (keystroke-level sending, newline behavior) and the exact semantics of each 'return' option, going beyond the schema's brief wording without redundancy.

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 opens with a specific verb and resource: 'Type a string of text into the focused window.' It immediately distinguishes itself from siblings by noting it does not focus anything and by naming alternatives like glass_set_value and glass_key, so an agent can tell exactly what this tool does.

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?

The description gives explicit when-to-use guidance: click the field first, prefer glass_set_value for a11y-exposed fields, send newline via glass_key separately, and use glass_do when multiple actions are known. It also states what happens if prerequisites are ignored ('text goes wherever focus already was'), leaving no ambiguity.

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