Type text into a selected element in a Perchance generator’s live preview or editor, with optional Enter submission. Use CSS or text selectors to automate form and UI input.
Type text into an element in the live preview (or editor chrome).
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to type | |
| frame | No | Default preview | |
| submit | No | Press Enter after typing. Default false | |
| timeout | No | ms. Default 10000 | |
| selector | Yes | CSS selector or 'text=...' |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden, and one sentence does not cover it. It never says whether existing content is cleared, whether the element is focused first, whether it waits for the element to appear, or how failures surface.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence with the action front-loaded and no filler. It is appropriately sized, though minimal to the point of under-specification for a five-parameter mutation tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Five parameters, no annotations, and no output schema leave the description responsible for behavioral context it does not provide. An agent still cannot tell what typing does to existing content or what a call returns, so it is incomplete for the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so all five parameters (text, frame, submit, timeout, selector) are already documented in the schema. The description's only added hint is the '(or editor chrome)' scope, which maps to the frame parameter but adds little beyond the enum already given.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 an element), plus scope (live preview or editor chrome). An agent can reasonably distinguish it from perch_click and perch_press, though it never explicitly names those siblings as alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance at all. The description does not say when to reach for perch_type versus perch_edit, perch_press, or perch_click, nor any prerequisites such as the element needing to be focusable or the preview being started.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.