Skip to main content
Glama
rsi-ai-platform

rsi-search-pro-mcp

Official

visit

Open and render JavaScript-heavy pages like single-page apps, charts, or login-walled sites with a real Chromium browser to extract text and screenshots.

Instructions

Open a URL with a real Chromium and return its rendered state.

Use when the cheaper fetch tools (web_fetch, pdf_fetch, http_post_form)
fail because the page is a SPA, JS-rendered chart, login-walled, or has
a dropdown that's not a separate URL.

Args:
    url: The page URL.
    wait_for_selector: Optional CSS selector to await before reading the
        DOM. Use when data appears only after an AJAX call returns —
        e.g. ".chart svg", "table#monthly tbody tr".
    wait_extra_ms: Extra settle time after the wait fires (default 1500).
    timeout_ms: Hard navigation timeout (default 45s).
    screenshot: Whether to capture a PNG INTERNALLY (default True). Adds
        ~200ms; the bytes are used by extract()/act() for Sonnet vision.
    full_page_screenshot: Scroll-stitch the whole page (default False).
    text_cap: Cap on extracted text length (default 30000).
    return_screenshot_b64: Whether to ECHO the base64 PNG back in the
        response. DEFAULT False — typical screenshots are 700KB-1MB and
        accumulating them across an agent's tool-call history blows the
        1M-token context window in ~3 calls. Only opt in when the caller
        actually consumes the bytes (e.g. a browser-canvas UI).

Returns:
    {url, title, domain, text, screenshot_bytes, screenshot_b64 (opt-in),
     fetched_at, current_date}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
wait_for_selectorNo
wait_extra_msNo
timeout_msNo
screenshotNo
full_page_screenshotNo
text_capNo
return_screenshot_b64No
Behavior4/5

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

No annotations provided, but description discloses use of real Chromium, screenshot size (~700KB-1MB), internal use by extract/act, text cap, and warnings about context window. Lacks mention of rate limits or redirect handling, but still very transparent.

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?

Well-structured with sections and bullet-like parameter explanations. Each sentence adds value, though slightly long due to necessary detail for 8 parameters.

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?

Covers all aspects: purpose, usage guidelines, parameter details, return values, and behavioral warnings. No output schema, so description fully explains output. Complete for a complex tool with 8 parameters.

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?

Schema coverage is 0%, but description compensates by explaining each of the 8 parameters with usage details, including default values, when to adjust, and impact (e.g., screenshot adds ~200ms, return_screenshot_b64 blows context).

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 clearly it opens a URL with Chromium and returns rendered state. Distinguishes from cheaper fetch tools by listing SPA, JS-rendered chart, login-walled, dropdown scenarios.

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?

Explicitly specifies when to use (when cheaper fetch tools fail) and provides reasons (SPA, JS-rendered, login-walled). Mentions alternative tools by name (web_fetch, pdf_fetch, http_post_form).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rsi-ai-platform/rsi-search-pro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server