Skip to main content
Glama
REX-codebase

Fable-mode

by REX-codebase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Activate a safe browser target

browser_click

Activates href links or submits safe GET forms via browser navigation, blocking POST and password fields to prevent credential leaks, then returns the resulting page status.

Instructions

Activates an href-bearing link or submits a GET form through normal browser navigation. POST and other form methods are refused, and GET forms containing password fields are blocked to prevent credential leakage. Returns the resulting page status or a bounded error without bypassing existing navigation controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
element_idYesStable element ID of an href-bearing link or submit control inside a safe GET form.
session_idNoOptional browser tab/session identifier.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.9
    • changedInput schema / properties / element_id / description
      Previous value: -"Stable element ID of an href-bearing link."New value: +"Stable element ID of an href-bearing link or submit control inside a safe GET form."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. First observedv1.3.2

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, the description adds meaningful behavioral constraints: POST is refused, password fields are blocked to prevent credential leakage, and errors are bounded without bypassing navigation controls. This gives agents important safety context beyond the structured annotation hints.

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?

Three compact sentences deliver purpose, restrictions, safety rationale, and outcome with no filler. The most important scoping information is front-loaded.

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?

Given the simple two-parameter schema, the output schema, and annotations, the description covers what the tool does, what it refuses, why it refuses it, and what it returns. No critical contextual gap remains.

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?

Schema description coverage is 100%, so the schema already documents both parameters. The description reinforces that element_id targets links or submit controls, but it does not add substantive new semantics beyond the schema.

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?

The description clearly states the specific action: activating an href-bearing link or submitting a GET form via normal browser navigation. It gives a concrete verb and target, though it does not explicitly contrast itself with sibling tools like browser_navigate.

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

Usage Guidelines4/5

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

The description specifies when the tool applies (links and GET forms) and explicitly excludes POST/other methods and password-containing GET forms. It provides clear conditions but does not name alternative sibling tools for divergent cases.

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