Skip to main content
Glama

Aginx Browser

by net.aginx
OverviewDiscussionsAdmin

session_input

Type text into an input/textarea element by its index (from session_state output), focusing it and dispatching input/change events. events:"full" is the complete human typing gesture: per-character keydown/keypress/input/keyup cycles, trailing change, then blur — the tail blur commits on forms that save in onBlur (React capture listeners, #100). In full mode a newline in the text types as the Enter key (key:'Enter', keyCode 13 — "type + Enter submit"): a textarea keeps the newline in its value, a single-line input stays single-line, the page's Enter listeners fire before the blur, and if the key wasn't canceled the input's form submits implicitly (Chrome's default action; preventDefault on the key or submit events vetoes it, so chat inputs that swallow Enter stay unsubmitted). Any characters — newlines, quotes, backslashes — ride through as-is. A refused fill answers filled:false with a reason (readonly/disabled/detached/no-element/wrong-tag/script-error) instead of a silent write. Hidden inputs are legitimate targets and are filled normally.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to type into the input field
indexYesElement index (from /state output)
eventsNoEvent fidelity: "full" types one character at a time with a keydown/keypress/input/keyup cycle per character, for pages whose listeners key on keyboard events (e.g. keypress-Enter login forms). Default fires a single input+change pair after the value is set.
session_idYesSession ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / title
      Removed value: -"SessionInputParams"
  2. Changed1 schema field changed
    • addedInput schema / properties / events
      Added value: +{
+  "default": null,
+  "description": "Event fidelity: \"full\" types one character at a time with a\nkeydown/keypress/input/keyup cycle per character, for pages whose\nlisteners key on keyboard events (e.g. keypress-Enter login forms).\nDefault fires a single input+change pair after the value is set.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations carry only a title, so the description bears the full burden and delivers: the exact event sequence in full mode, the trailing blur/onBlur commit behavior, Enter/newline semantics including implicit form submission and veto conditions, passthrough of arbitrary characters, and an explicit refusal contract (filled:false with readonly/disabled/detached/no-element/wrong-tag/script-error reasons). This is exceptionally rich behavioral disclosure.

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?

Purpose is front-loaded and virtually every clause carries substantive information (blur commit, Enter handling, refusal reasons). It is a dense single paragraph with heavy parenthetical nesting, which slightly impairs scanability, but there is little wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description compensates fully: it documents side effects (focus, dispatched events, blur), edge cases (hidden inputs, newlines/quotes/backslashes), Enter-submit behavior, and the failure response shape. An agent has everything needed to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description goes beyond the schema by elaborating what 'events:"full"' actually does (per-character keydown/keypress/input/keyup cycles, trailing change, blur) and by clarifying the index origin, adding real meaning over the schema's terse enum-like description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 into an input/textarea element by its index' — and clarifies the index source (session_state output), which cleanly separates it from siblings like session_click or session_eval. An agent can identify what it does without opening the schema.

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?

It explains what the 'events:"full"' mode is for ('type + Enter submit', keypress-Enter login forms) and where the index comes from, which is implicit usage guidance. However, it never explicitly states when to choose this tool over session_eval, session_click, or other input paths, and offers no when-not-to-use conditions.

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

All Aginx Browser toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources