Skip to main content
Glama
linux-computer-use-mcp

linux-computer-use-mcp

by dhakseshr

type_text

Types text into the focused field as keyboard input; newlines press Enter. Use it to enter data or commands in a live Linux desktop session.

Instructions

Type text into the focused field, as if from the keyboard. Newlines press Enter.

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

Input Schema

NameRequiredDescriptionDefault
textYes
screenshotNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that embedded newlines act as Enter keypresses, which is real behavioral information, but it says nothing about what happens when no field is focused, whether input is sent at typing speed, or what the screenshot side effect does.

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 with no filler, and the core action is front-loaded ahead of the newline caveat. Nothing could be removed without losing information.

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?

For a simple two-parameter action tool with no output schema, the description covers the main behavior adequately. The unexplained screenshot parameter and the unstated focus prerequisite leave meaningful gaps for an agent deciding whether it can call this now.

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 coverage is 0%, so the description must compensate for both parameters. It clarifies the semantics of `text` (newline handling) reasonably well, but the `screenshot` parameter — a non-obvious, default-true side effect — is never mentioned or explained anywhere.

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 uses a specific verb and resource ('Type text into the focused field') and adds a mental model ('as if from the keyboard'), which separates it from press_key and hold_key. It stops short of naming the sibling it contrasts with, but the action is unambiguous.

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

Usage Guidelines3/5

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

'Into the focused field' implies a prerequisite (the target must already be focused, via click or focus_window), but this is left implicit. There is no explicit statement of when to use this instead of press_key or batch, nor any exclusion or failure condition.

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