Skip to main content
Glama

Fetches one public web page you name and returns its title

search_rag_web_browser
Read-only

Fetches one public web page you name (http or https) and returns its title, canonical URL and readable text as Markdown-like text (headings, links, list items; scripts and styles removed, capped at 20,000 characters). Pages that need login or run only in JavaScript return little text. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "url": "<url>"
    },
    "name": "search_rag_web_browser"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http or https page URL, up to 500 characters

Output Schema

NameRequiredDescriptionDefault
urlNo
textNo
titleNo
sourceNo
checkedAtNo
truncatedNo
canonicalUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds substantial behavior the annotations do not carry: scripts/styles stripped, Markdown-like output capped at 20,000 characters, degraded results on login-gated or JS-only pages, and a $0.002 per-successful-call x402 charge with failures uncharged. Cost and failure-billing semantics are exactly the kind of context annotations cannot express, though it stops short of covering redirects, timeouts, or rate limits.

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?

One dense passage that front-loads the action and return shape, then layers limitations and pricing. Every clause — including the character cap and the failed-call billing exemption — carries decision-relevant information with no filler.

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?

A one-parameter fetch tool with an output schema, so return values need no explanation; the description instead covers the things that actually determine correct invocation: input format, output trimming, JS/login failure mode, and payment model. Nothing material is missing for an agent deciding whether and how to call it.

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% and the single `url` parameter already documents "Public http or https page URL, up to 500 characters." The description restates the http/https constraint and adds nothing about format normalization, redirect targets, or fragment handling, so the baseline 3 applies.

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 a concrete verb and resource ("Fetches one public web page you name (http or https)") and enumerates what comes back: title, canonical URL, and readable text. That specificity is enough for an agent to tell this apart from the loosely related data-lookup siblings, none of which fetch arbitrary URLs.

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?

Gives a clear usage condition (any public http/https page) and an explicit when-it-fails caveat: "Pages that need login or run only in JavaScript return little text." It does not point to an alternative tool for those cases, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources