Skip to main content
Glama
Sign In

Profullstack

by com.profullstack
OverviewDiscussionsAdmin

Obscura: Fetch Web Page

obscura_fetch_page
Read-onlyIdempotent

[Obscura] Fetch a public web page through Obscura, a stealth headless browser that renders JavaScript and presents Chrome's TLS fingerprint, so pages that answer curl with 403 usually answer this. Returns the page as markdown (default), plain text, its links, the rendered HTML, or the original bytes. No credential needed.

Served by Obscura (https://obscura.openmcp.logicsrc.com).

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": "obscura_fetch_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe page, http or https, on a public host.
formatNomarkdown (default) for reading; text for a plain dump; links for every href; html for the rendered DOM (large); original for the raw response body, best for feeds and XML.
stealthNoChrome 145 TLS fingerprint and tracker blocking. Default true.
max_charsNoCut the answer to this many characters. Default 200000.
timeout_secondsNoNavigation timeout. Default 30, at most 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that with the JavaScript rendering, TLS fingerprinting, stealth default and credential-free access, but says nothing about rate limits, failure modes, or whether pages are cached.

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?

Two sentences, both front-loaded with the capability then the return options, plus a short attribution line. The format list partially duplicates the schema enum and could be trimmed, but nothing is genuinely wasted.

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?

For a single-URL fetch tool with no output schema, the description should carry the burden of describing the shape of the result. It names the five output formats but does not describe the response structure (e.g. how links or errors are surfaced), leaving a moderate gap for an agent interpreting results.

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 description coverage is 100%, so every parameter is already documented with defaults and bounds in the schema itself. The description's enumeration of output formats largely restates the format enum rather than adding new semantics, so this is the correct baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource ('Fetch a public web page') and explains the mechanism that makes it distinct: a stealth headless browser with Chrome's TLS fingerprint so 403-answering pages work. It differentiates from generic HTTP clients like curl, but never names the clearly related sibling tronbrowser_fetch_page, so the agent has no guidance on how this differs from it.

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 use case ('pages that answer curl with 403 usually answer this') and reassures that 'No credential needed,' which is useful context for adoption. It offers no when-not-to-use guidance and no pointer to an alternative tool, so it stops short of explicit routing.

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

All Profullstack toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources