Skip to main content
Glama

gui_type

Destructive

Types short text into the currently focused GUI element after explicit local GUI opt-in.

Instructions

Type short text into current focused GUI element, requires explicit local GUI opt-in

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": {
      "text": "<text>"
    },
    "name": "gui_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=false, so the safety profile is supplied. The description nonetheless adds meaningful context beyond them: input goes to whatever is currently focused (no element targeting), the payload is expected to be short, and an explicit local opt-in is required. It does not explain why the operation is flagged destructive, e.g. that text could land in the wrong field if focus drifted.

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 clause pairs the action with its scope, and the opt-in caveat follows immediately; there is no filler. The phrasing is slightly compressed, packing scope, target, and prerequisite into one comma-joined sentence.

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?

For a one-parameter tool with annotations covering safety, this is close to sufficient, but the focus-dependent nature of the action (how focus is established, what happens on failure) is unstated. An agent knows what the tool does but not the surrounding workflow needed to call it reliably.

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 description coverage is 0% for the single parameter, though maxLength 3000 in the schema constrains size. The description only echoes "short text" without noting whether newlines, special characters, or Unicode are supported, or whether existing content is replaced or appended. With only one parameter the gap is small but real.

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 a specific verb ("Type") and resource ("current focused GUI element") and scopes the payload as "short text", which is enough to distinguish it from gui_click and gui_hotkey by name alone. It stops short of explicitly saying how it differs from the browser_fill sibling, which is the closest functional alternative.

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?

It gives one real prerequisite ("requires explicit local GUI opt-in"), which tells the agent the tool may be unavailable without configuration. It says nothing about when to prefer this over browser_fill for web input, nor that focus must be established first (e.g. via gui_click), so the choice between siblings is left to inference.

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