Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_text

Retrieve compact visible text lines from a webpage. Ideal for reading or searching page content without overwhelming context.

Instructions

Return compact visible text lines from the page. Prefer this before browser_snapshot when you need to read/search page content without flooding context.

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_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNo
queryNoOptional case-insensitive substring filter.
limitNoMaximum lines returned (capped at 300).
maxCharsNoMaximum total characters returned (capped at 20000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes the output as 'compact visible text lines' and mentions caps, but does not disclose whether hidden text is excluded, how line breaks are handled, or the exact return format. This is adequate but lacks detail.

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?

The description is two sentences, front-loaded with purpose, and every sentence adds value. No wasted words.

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

Completeness3/5

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

Given the absence of an output schema, the description does not explain the return structure (e.g., array of strings with line numbers). It mentions 'lines' but not format. The tool is simple, but the missing output format is a gap for correct invocation.

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 coverage is 75% (tabId lacks description). The description adds value beyond schema: query is case-insensitive, limit is capped at 300, maxChars at 20000. These details are not in the schema and help the agent make informed choices.

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 returns 'compact visible text lines from the page', which is a specific verb and resource. It explicitly distinguishes this tool from its sibling 'browser_snapshot' by advising preference for reading/searching without flooding context.

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 provides clear context: use when you need to read/search page content without flooding context, and prefer this before browser_snapshot. However, it does not explicitly state when not to use it (e.g., if full HTML is needed), leaving room for ambiguity.

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