Skip to main content
Glama

desktop_type

Insert text into a resolved desktop text target, with optional keystroke interval and timeout settings to control input timing.

Instructions

agent-desktop type: Insert text into a text target

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": {
      "ref_id": "<ref_id>"
    },
    "name": "desktop_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoText to type
ref_idYesQualified ref from snapshot (@<snapshot_id>:eN)
timeout_msNoMaximum wait in milliseconds, covering ref resolution, actionability and delivery of the text; default 5000 plus 30 per character of TEXT; 0 disables the wait
interval_msNoType one keystroke every N ms (1-2000) instead of inserting TEXT at once; --timeout-ms then applies to each keystroke, and 0 makes each keystroke try once

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description fully carries the behavioral burden yet says nothing about the tool being an acting/mutating operation on a live desktop, focus or actionability requirements, or failure behavior when the ref is stale. Only the schema's timeout wording hints at the ref-resolution and actionability waits.

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

Conciseness3/5

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

One short sentence with no wasted words, front-loaded with the tool family and verb. However, the brevity stems from under-specification rather than disciplined editing — nothing about prerequisites or behavior is included.

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

Completeness2/5

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

For a four-parameter desktop-automation action with no annotations and no output schema, the description leaves out the ref-acquisition prerequisite, the fact that text is optional despite being the core action, and any indication of what a successful or failed invocation looks like.

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 100%, so the schema already explains text, ref_id, timeout_ms and interval_ms in detail. The description adds no meaning beyond that, which puts it at the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Insert text into a text target" gives a verb plus a resource, but "text target" remains undefined — it is only clarified indirectly by the ref_id schema note about snapshot refs. It does not distinguish the tool from its sibling input tools such as desktop_key_down/desktop_key_up.

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?

No when-to-use guidance is given: nothing says to prefer this over per-keystroke typing (interval_ms) or over key_down/key_up, and no prerequisite (obtaining a ref from a snapshot) is stated. The agent must infer the entire invocation context.

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