Skip to main content
Glama
Sign In
ecobrowser MCP server

ecobrowser MCP server

by HaidarESBER
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_read_text

Extract the visible text content from the current web page for AI processing, with automatic truncation to prevent overload.

Instructions

Return the visible text content of the current page (truncated).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_read_text"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions truncation but does not specify truncation limits or whether the method is non-destructive. For a read operation, basic safety is implied but not stated, and dynamic content behavior is unaddressed.

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?

Single sentence, no wasted words, front-loaded with the core action. Highly concise and efficient.

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 tool with no parameters, no output schema, and no annotations, the description is adequate but could elaborate on truncation behavior or indicate that returns plain text. Sibling tools are present but not compared. Slightly incomplete for full context.

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?

There are no parameters (schema has no properties), and schema description coverage is 100%. Description adds no parameter information, but baseline is 4 for zero-parameter tools since there is nothing to explain.

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?

Description clearly states the tool returns visible text content of the current page, with truncation noted. Verb 'Return' and resource 'visible text content' are specific, and 'truncated' adds an important detail. It distinguishes well from siblings like browser_snapshot or browser_find.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like browser_snapshot or browser_changes. No when-not-to-use or prerequisites are mentioned, leaving the agent to infer usage from the name alone.

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