Skip to main content
Glama
Sign In
ecobrowser MCP server

ecobrowser MCP server

by HaidarESBER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_find

Locate interactive elements on a page by description (e.g., 'login button') and return their IDs, saving time vs. scanning the full snapshot.

Instructions

Find interactive elements matching a description (e.g. 'search box', 'Sign in button') and get just the matches with their ids — far cheaper than reading a full snapshot when you know what you want.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "browser_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat to look for, e.g. 'login button'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It describes the action (find) and output (matches with ids), but omits details like whether it modifies state, searches hidden elements, or requires a loaded page. Adequate but not comprehensive.

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?

The description is a single, well-structured sentence that front-loads the action. It is slightly verbose due to examples and comparison, but remains efficient and clear.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description covers the input, action, output, and rationale. It is sufficiently complete for an agent to understand and invoke the tool correctly.

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 coverage is 100% with a clear parameter description. The tool description reinforces the schema with additional examples. Since the schema already provides the necessary semantics, the description adds only marginal value.

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?

The description clearly states the tool's purpose: 'Find interactive elements matching a description' and gives concrete examples ('search box', 'Sign in button'). It distinguishes from siblings by highlighting cost savings over a full snapshot.

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 implicitly advises when to use this tool: 'far cheaper than reading a full snapshot when you know what you want.' It does not explicitly name alternatives or state when not to use, but the context suggests it is for targeted element discovery.

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