Type text into an input/textarea element by its index (from session_state output).
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Text to type into the input field | |
| index | Yes | Element index (from /state output) | |
| session_id | Yes | Session ID |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide no behavioral hints (no readOnly/destructive flags), so the description carries the full burden. It states that the tool types text, implying a write operation, but does not disclose side effects (e.g., overwriting existing text) or any prerequisites like session activity. This is minimal but not misleading.
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 sentence, front-loaded with the verb and target, and includes the key usage note about the index source. No redundancy or unnecessary detail—every word earns its place.
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?
For a simple text-entry tool with three fully described parameters and no output schema, the description provides adequate context to use the tool correctly. It explains what it does and where to get the index, though it omits potential error scenarios or behavior when the element is not found. Overall, sufficient 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?
The schema covers 100% of parameters, so the baseline is 3. The description adds value by clarifying that the index refers to elements from session_state output and that the target is specifically an input/textarea element—details not present in the schema. This enriches the parameter understanding.
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?
The description clearly states the action ('Type text') and the target resource ('input/textarea element'), with a specific scoping mechanism ('by its index'). It distinguishes itself from sibling tools like click, eval, and fetch by explicitly indicating text entry.
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?
The description provides useful context on how to obtain the index: it must come from session_state output. This implicitly tells the agent to retrieve the index via the session_state tool first. No alternatives or exclusions are mentioned, but the context is clear enough for this tool's purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there's overlap between session_click/click and session_eval/eval. Descriptions clarify that session_* tools operate on persistent sessions while the others are one-off, so ambiguity is low.
The session_* prefix is consistently used for session-related tools (17 of 23), while the remaining tools (cache, click, download, eval, fetch, search) are single-word lowercase verbs. This is a clear pattern, though not strictly verb_noun.
23 tools is above the typical 3-15 range but reasonable for a browser automation server that needs both one-off and session-based operations. The count is justified by the breadth of features, though it's slightly heavy.
The surface covers all major browser automation needs: navigation, clicking, typing, scrolling, screenshot, state inspection, console/network logs, cookies/storage management, JavaScript eval, waiting, and even session export. No obvious gaps for the stated purpose.