Skip to main content
Glama

type

Enters text into the currently focused input field on a live cloud device, letting agents fill forms and submit queries during UI verification.

Instructions

Type text into the currently focused input field.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to type into the focused field. On a phone or tablet a line break presses Enter, which submits the field (bash: $'query\n'); `press enter` does the same.
session_idNoSession ID to target. Optional: falls back to the MCP-server-held dev_start session, then this project's `vibeview dev --detach` state, if either is available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only supply readOnlyHint=false, so the description does add value by surfacing the focus precondition. However, it does not disclose whether text is appended at the cursor or replaces existing content, nor does it repeat the line-break-submits-field behavior that lives only in the schema's parameter description.

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?

A single short sentence, front-loaded with the verb and the key precondition. Nothing extraneous.

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 input tool with full schema coverage and no output schema, this is minimally sufficient. Gaps remain around append-vs-replace semantics and the need to focus a field first, which matter for correct invocation.

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%, including the useful note that a line break acts as Enter and submits the field. The tool description contributes nothing about the `text` or `session_id` parameters, so it is baseline at best.

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 (type) and resource (text into the currently focused input field), which is enough to tell it apart from sibling tools like clear_text or press. It stops short of naming any sibling explicitly, so it sits just below the top band.

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?

The phrase 'currently focused input field' implies a prerequisite (something must be focused first, e.g. via `focus`), but the description never says so directly and never mentions clear_text as the alternative when existing text must be replaced. Usage guidance is inferable rather than stated.

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