Skip to main content
Glama

clear_text

Clears text in the currently focused input field so coding agents can reset forms and remove unwanted input before entering new values.

Instructions

Clear the text in the currently focused input field.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clear_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.4/5.0
Behavior3/5

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

readOnlyHint=false is declared, and the description is consistent with a mutating action rather than contradicting it. It adds the useful detail that the operation is implicit-target (acts on whatever has focus, taking no element reference), but it does not say what happens when no input is focused, whether the cleared text is recoverable, or what the call returns.

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

Conciseness4/5

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

A single front-loaded sentence with zero filler and the scoping qualifier ('currently focused') placed before the object. It is appropriately sized, though it sits near the terse edge given the unaddressed focus precondition.

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 one-optional-parameter action tool with a fully described schema and a single declared annotation, this is close to adequate. However, with no output schema present, the description leaves the agent without any sense of the return value or failure mode when no input field 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?

The single optional `session_id` parameter is fully documented in the schema at 100% coverage, including the fallback chain to the server-held dev_start session and project dev state. The description adds nothing about it, so the baseline 3 applies when the schema does all the work.

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?

Names a specific verb ('Clear') and resource ('the text in the currently focused input field'), which is concrete enough to distinguish it from the sibling set (tap, press, find, focus). No explicit contrast with a sibling is offered, but none of the listed siblings plausibly overlaps, so the 4 rather than 5.

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 precondition (a field must already be focused, likely via the `focus` sibling) but never states it as a requirement or names `focus` as the prerequisite step. There are no stated exclusions or alternatives, so guidance is only implied.

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