Skip to main content
Glama

set_text

Replace the contents of a text box from the last read_window with new text; password boxes are refused for safety.

Instructions

Replace the contents of a text box from the last read_window. Password boxes are refused.

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": {
      "handle": "<handle>",
      "ref": "<ref>",
      "text": "<text>"
    },
    "name": "set_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes
textYes
handleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the state dependency on the last read_window and that password boxes are rejected, but says nothing about failure modes for stale handles or invalid refs, whether the window must be focused, or whether the replacement is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, the core action first and the constraint second. Every clause carries information and nothing is padded.

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?

An output schema exists so return values need not be described, and the mutation plus one refusal case are covered. However, for a three-parameter write tool operating on a GUI with zero schema coverage, the missing explanation of handle/ref and error behavior leaves real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain ref, text, and handle. It only implicitly hints that 'text box' maps to ref and contents to text; the 'handle' parameter and its relationship to 'the last read_window' are left entirely unexplained.

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 states a specific verb and resource ('Replace the contents of a text box') and scopes it to 'the last read_window', which clearly separates it from read_window, click, and list_windows. It falls short of a 5 only because it doesn't name an alternative write tool it might be confused with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an implicit precondition (a read_window must have happened first, since the target comes from the last one) and an explicit exclusion ('Password boxes are refused'). No named alternatives or guidance for non-text-box targets, so not a full 5.

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

Deploy Server

Other Tools