Skip to main content
Glama
alderban107

hyprland-mcp

by alderban107

type_text

Simulate keyboard input to type text into applications with configurable keystroke delay for automation workflows.

Instructions

Type text as if from a keyboard.

Args: text: The text to type delay_ms: Delay between keystrokes in milliseconds (0 = instant)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
delay_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler implementation for type_text which uses wtype to simulate keyboard input.
    async def type_text(text: str, delay_ms: int = 0) -> None:
        """Type text using wtype."""
        require_tool("wtype")
        cmd = ["wtype"]
        if delay_ms > 0:
            cmd.extend(["-d", str(delay_ms)])
        cmd.extend(["--", text])
    
        proc = await asyncio.create_subprocess_exec(
            *cmd,
            stdout=asyncio.subprocess.PIPE,
            stderr=asyncio.subprocess.PIPE,
        )
        _, stderr = await proc.communicate()
        if proc.returncode != 0:
            raise InputError(f"wtype failed: {stderr.decode().strip()}")
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool types text with a delay, implying a write operation, but lacks details on permissions needed, side effects (e.g., focus requirements), error conditions, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 front-loaded with a clear purpose statement, followed by concise parameter explanations. Every sentence earns its place by adding value, though the structure could be slightly improved by integrating usage context. It avoids redundancy and is appropriately sized for the tool's complexity.

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?

Given the tool's moderate complexity (2 parameters, no annotations, but with an output schema), the description is partially complete. It covers the basic action and parameters but lacks behavioral details like focus requirements or error handling. The presence of an output schema reduces the need to explain return values, but more context is needed for safe use.

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?

The description adds meaningful context for both parameters beyond the schema's 0% coverage. It explains that 'text' is 'The text to type' and 'delay_ms' defines 'Delay between keystrokes in milliseconds (0 = instant)', clarifying their roles and the default behavior. This compensates well for the low schema coverage.

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 the tool's purpose with a specific verb ('Type') and resource ('text'), and it distinguishes itself from siblings like 'key_press' (single keys) and 'type_into' (context-specific typing) by focusing on general keyboard text input. The phrase 'as if from a keyboard' adds clarity about the simulation aspect.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'type_into', 'key_press', or 'send_shortcut'. It mentions no prerequisites, exclusions, or specific contexts, leaving the agent to infer usage from the tool name alone without explicit direction.

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/alderban107/hyprland-mcp'

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