Skip to main content
Glama

macos_keyboard_type

Types arbitrary text into the focused macOS element using Unicode injection, enabling layout-independent entry of capitals, symbols, accents, and emoji.

Instructions

macOS only. Type arbitrary text into the focused element. Injects Unicode directly, so it is layout-independent and correctly produces capitals, symbols, accented letters, and emoji. Use this for entering text; use macos_keyboard_press for named keys (Enter, Tab) and shortcuts. Requires Accessibility permission.

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": "macos_keyboard_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text to type. Injected as Unicode, so it is layout-independent and handles any characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and mostly meets it: it discloses the Unicode injection mechanism, layout independence, character coverage including emoji, and the Accessibility permission requirement. It stops short of saying what happens on failure (missing permission, no focused element) or whether existing field content is replaced or appended.

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?

Four short sentences, each earning its place: platform constraint first, then behavior, then capability, then routing advice, then permission. Front-loaded and free of filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter text-input tool with no output schema, this covers mechanism, platform, permission, and alternatives. The remaining gap is failure-mode behavior when permission is not granted or no element is focused.

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?

With a single parameter at 100% schema description coverage, the schema already documents 'text' thoroughly, including the Unicode/layout-independent behavior. The description largely restates that same property, adding little parameter-specific meaning beyond it.

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 names a specific verb and resource ('Type arbitrary text into the focused element') and immediately scopes it with 'macOS only.' It distinguishes itself from the keyboard sibling tool by contrasting text entry with named-key presses.

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?

It explicitly states when to use this tool ('Use this for entering text') and names the alternative and its condition ('use macos_keyboard_press for named keys (Enter, Tab) and shortcuts'). It also states the prerequisite: Accessibility permission.

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