Skip to main content
Glama

desktop_type

Destructive

Type text on a desktop session, where the keyboard focus is (click a field first). Up to 500 characters; a newline presses Enter. The user started this desktop session for you in Termalin and can watch it. Coordinates are pixels of your last desktop_screenshot. Never type passwords, keys or other secrets: when a sign-in or secret is needed, stop and ask the user to type it themselves.

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

Input Schema

NameRequiredDescriptionDefault
textYesThe text to type
session_idYesDesktop session id from desktop_list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a 500-character cap, newline mapping to Enter, and the fact that the user can watch the session in Termalin—useful given destructiveHint=true and openWorldHint=true. It does not warn that Enter may submit/commit an action irreversibly, and the note about screenshot coordinates is irrelevant to typing and mildly confusing.

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?

Front-loaded with the core action and the safety rule, and most sentences earn their place. The sentence about coordinates being pixels of the last desktop_screenshot does not apply to a typing tool and dilutes an otherwise tight definition.

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?

Covers action, precondition, input limits, and safety policy for a two-parameter mutation tool with no output schema. Missing only a hint about what the call returns or fails on (e.g., session not focused, session gone).

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?

Schema coverage is 100%, so the baseline is 3; the description still adds value by defining the constraints on `text` (500 chars, newline semantics) that the schema omits. `session_id` sourcing is already fully documented in the schema.

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?

States a specific verb and resource ("Type text on a desktop session") and pins the precondition clearly ("where the keyboard focus is (click a field first)"), which separates it from desktop_click. It does not explicitly distinguish itself from desktop_key, so an agent must infer that special/named keys belong to that sibling.

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?

Gives a concrete precondition (click a field first) and an explicit prohibition/routing rule: never type secrets, stop and ask the user instead. Lacks guidance on when to prefer desktop_key over desktop_type for non-text input.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.