Skip to main content
Glama
REX-codebase

Fable-mode

by REX-codebase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Replace text field value

browser_type

Replace text in a specified input or textarea field without submitting the form. Returns status and element ID; errors for missing or non-editable fields.

Instructions

Replaces the full value of a text-like input or textarea identified by element_id; it does not submit the form. Use browser_press for single-key edits or activation. An omitted session_id targets the active/default session. Returns status typed, the element ID, and the supplied text; missing or non-editable elements return an error object and are not changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText content to enter into element.
element_idYesStable element ID to type into.
session_idNoOptional browser tab/session identifier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.5
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv1.3.2

TDQS

A5/5.0
Behavior5/5

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

Discloses error behavior for missing or non-editable elements (returns an error object and does not change them), confirms no form submission, and describes the return payload (status 'typed', element ID, supplied text). This goes well beyond the sparse annotations.

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?

Two sentences pack the main effect, alternative usage, session default, return value, and error behavior with zero filler, front-loading the core action.

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?

The description covers selection, invocation, session handling, and success/failure results. Sibling differentiation and output schema remove remaining ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds meaning: 'full value' and 'text-like input or textarea' clarify text/element_id semantics, and the session_id default behavior is specified.

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 precise verb+resource: replaces the full value of a text-like input or textarea identified by element_id. Explicitly notes that it does not submit the form, distinguishing it from activation and navigation siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names browser_press as the alternative for single-key edits or activation, giving an agent actionable routing criteria. Also clarifies that an omitted session_id targets the active/default session.

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

Deploy Server

Other Tools