Skip to main content
Glama
Touchpoint-Labs

Touchpoint

by Touchpoint-Labs
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

type_text

Type text into the focused element on any desktop app using simulated keyboard input with support for special keys like Enter, Tab, and Backspace.

Instructions

Type text into the currently focused element.

Simulates keyboard input.  Focus a text field first with
click() or focus(), then type into it.

Special characters:
  \n = Enter (line break),  \t = Tab (next field),
  \b = Backspace (delete previous character).

Args:
    text: The text to type.
    raw: If true, type literal backslashes without converting
        ``\n``, ``\t``, or ``\b`` escape sequences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
rawNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

With no annotations, the description bears full burden. It discloses keyboard simulation, special character handling (\n, \t, \b), and raw mode. Missing details on clearing existing text, but overall adequate.

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?

Concise yet complete: two short paragraphs plus bullet-like arg definitions. Every sentence adds value, no redundancy.

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 simplicity and presence of output schema, the description covers prerequisites, parameter details, and special characters. No gaps for intended usage.

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

Parameters5/5

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

Schema coverage is 0%, and the description fully compensates by explaining both 'text' (the string to type) and 'raw' (literal backslash behavior) with clear semantics and examples.

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 clearly states 'Type text into the currently focused element' with a specific verb and resource. It distinguishes from siblings like select_text and set_value by emphasizing simulation of keyboard input.

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?

Explicitly instructs to focus an element first using click() or focus(), providing clear prerequisite and usage context. Could mention alternatives but is sufficient.

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/Touchpoint-Labs/Touchpoint'

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