Skip to main content
Glama
O-mega-Enterprise

suprsonic-mcp

by O-mega-Enterprise
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

scrape

Extract content from any URL as Markdown, HTML, or raw HTML with fast, standard, or thorough rendering modes.

Instructions

Extract content from any URL as Markdown or HTML. Cost: fast 1 credit, standard 2 credits, thorough 5 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to scrape.
modeNoMode: fast (Raw HTTP, no JS. <1s), standard (Full JS rendering. 2-5s), thorough (Anti-bot proxies + JS rendering. 10-30s).
outputNoContent format.markdown
timeoutNoSeconds the page may take to load (up to 55).
wait_forNoCSS selector to wait for (standard and thorough modes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.1
    • removedInput schema / properties / mode / default
      Removed value: -"standard"
    • changedInput schema / properties / mode / description
      Previous value: -"fast (1 credit, static HTML), standard (2 credits, JS rendering), thorough (5 credits, stealth + CAPTCHA)"New value: +"Mode: fast (Raw HTTP, no JS. <1s), standard (Full JS rendering. 2-5s), thorough (Anti-bot proxies + JS rendering. 10-30s)."
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "fast",
+  "standard",
+  "thorough"
+]
    • changedInput schema / properties / output / description
      Previous value: -"markdown, html, or raw_html"New value: +"Content format."
    • addedInput schema / properties / output / enum
      Added value: +[
+  "markdown",
+  "html",
+  "raw_html"
+]
    • addedInput schema / properties / timeout
      Added value: +{
+  "default": 30,
+  "description": "Seconds the page may take to load (up to 55).",
+  "type": "number"
+}
    • changedInput schema / properties / url / description
      Previous value: -"URL to scrape"New value: +"URL to scrape."
    • addedInput schema / properties / wait_for
      Added value: +{
+  "description": "CSS selector to wait for (standard and thorough modes).",
+  "type": "string"
+}
  2. First observedv0.3.0

TDQS

A3.5/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 the full burden. It adds genuine behavioral value by disclosing per-mode credit costs, which appear nowhere in the schema, but says nothing about auth needs, rate limits, retry/error behavior, or what happens on blocked pages.

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?

Two tight sentences with zero waste: purpose first, cost second. Every clause earns its place and nothing is padded.

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?

With 5 parameters at 100% schema coverage and no output schema, the description is close to sufficient. The credit-cost disclosure is a useful addition, though an agent gets no signal about failure modes or scraping restrictions on a tool that explicitly has anti-bot modes.

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 100%, so the baseline is 3, and the description adds above-baseline meaning by mapping each mode enum value to a specific credit cost ('fast 1 credit, standard 2, thorough 5') — a mapping the schema does not contain. It does not touch url, output, timeout, or wait_for, but those are already fully documented.

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 specific verb and resource ('Extract content from any URL') plus the output formats (Markdown or HTML), so the agent knows exactly what comes back. It is distinguishable from siblings like screenshot or site-intel by its raw-content-extraction framing, though it never names or contrasts with any sibling explicitly.

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 when-to-use or when-not-to-use guidance, and no alternatives named among the 23 sibling tools. The credit-cost line hints at a cheap-vs-expensive tradeoff between modes but gives no rule for choosing the tool itself over search or site-intel.

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