Skip to main content
Glama
dmytrome

Groundhog

by dmytrome
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Read a URL

read_url
Read-only

Fetch a web page through a stealth browser to get clean, readable content even from sites that block plain fetchers, with hidden text flagged and a provenance receipt for grounding.

Instructions

Fetch one web page through the stealth browser and return clean, grounded content with provenance.

Hidden text injected for models but invisible to humans is stripped by default and reported in threats. Use this to ground answers in live web content, including sites that block plain fetchers.

Reads a URL you already have: use search to find URLs, or research to search and read in one call. Fetches are rate limited per domain (5s apart by default), so several pages from one site are not instant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL. Private and loopback addresses are refused.
queryNoWhen set, `matches` carries the passages most relevant to it, each with its heading and offset for citation.
formatNo'markdown' extracts the article; 'text' returns the page's rendered text.markdown
max_tokensNoToken budget for the content. Omit to use the server's GROUNDHOG_MAX_TOKENS (20000 by default). Must be positive.
include_hiddenNoKeep text that is invisible to a human reader. It is reported in `threats` either way; this only controls whether it stays in the content.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
titleYes
statusYes
matchesYes
threatsYes
markdownYes
final_urlYes
set_asideYes
truncatedYes
fetched_atYes
provenanceYes
http_statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.16.1
    • addedOutput schema / properties / set_aside
      Added value: +{
+  "title": "Set Aside",
+  "type": "integer"
+}
    • changedOutput schema / required
      Previous value: -[
-  "markdown",
-  "title",
-  "url",
-  "final_url",
-  "fetched_at",
-  "status",
-  "http_status",
-  "truncated",
-  "threats",
-  "matches",
-  "provenance"
-]New value: +[
+  "markdown",
+  "title",
+  "url",
+  "final_url",
+  "fetched_at",
+  "status",
+  "http_status",
+  "truncated",
+  "threats",
+  "matches",
+  "set_aside",
+  "provenance"
+]
  2. Changed1 schema field changedv0.15.0
    • addedOutput schema / $defs / Threat / properties / seen
      Added value: +{
+  "title": "Seen",
+  "type": "integer"
+}
  3. Changed1 schema field changedv0.13.0
    • changedOutput schema / $defs / Threat / properties / type / enum
      Previous value: -[
-  "hidden_css",
-  "report_truncated",
-  "final_url_suppressed",
-  "detection_degraded",
-  "strip_incomplete",
-  "zero_width",
-  "bidi",
-  "tag"
-]New value: +[
+  "hidden_css",
+  "hidden_attribute",
+  "hidden_template",
+  "report_truncated",
+  "final_url_suppressed",
+  "detection_degraded",
+  "strip_incomplete",
+  "zero_width",
+  "bidi",
+  "tag"
+]
  4. Changed3 schema fields changedv0.10.0
    • addedOutput schema / properties / http_status
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Http Status"
+}
    • addedOutput schema / properties / status
      Added value: +{
+  "enum": [
+    "ok",
+    "challenge",
+    "blocked",
+    "rate_limited",
+    "not_found",
+    "server_error",
+    "unsupported_content",
+    "unknown"
+  ],
+  "title": "Status",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "markdown",
-  "title",
-  "url",
-  "final_url",
-  "fetched_at",
-  "truncated",
-  "threats",
-  "matches",
-  "provenance"
-]New value: +[
+  "markdown",
+  "title",
+  "url",
+  "final_url",
+  "fetched_at",
+  "status",
+  "http_status",
+  "truncated",
+  "threats",
+  "matches",
+  "provenance"
+]
  5. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / format / description
      Added value: +"'markdown' extracts the article; 'text' returns the page's rendered text."
    • addedInput schema / properties / include_hidden / description
      Added value: +"Keep text that is invisible to a human reader. It is reported in `threats` either way; this only controls whether it stays in the content."
    • addedInput schema / properties / max_tokens / description
      Added value: +"Token budget for the content. Omit to use the server's GROUNDHOG_MAX_TOKENS (20000 by default). Must be positive."
    • addedInput schema / properties / query / description
      Added value: +"When set, `matches` carries the passages most relevant to it, each with its heading and offset for citation."
    • addedInput schema / properties / url / description
      Added value: +"Absolute http(s) URL. Private and loopback addresses are refused."
  6. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint. The description adds substantial behavioral detail: stealth browser usage, hidden-text stripping with reporting in `threats`, and rate limiting. This goes well beyond the annotations and paints a clear picture of what happens when the tool runs, with no contradiction.

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 compact—three sentences—and front-loads the core purpose, then adds usage guidance and a behavioral caveat. Every sentence earns its place without redundancy or fluff.

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?

With an output schema present, the description need not detail return values. It covers usage context (when to use vs siblings), behavioral nuances (hidden text, rate limits), and points to alternative tools. Nothing an agent needs to correctly select and call this tool is missing.

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 the schema already documents every parameter. The description adds little beyond what the schema provides; it mentions the query behavior implicitly via 'ground answers' but does not add new semantic details. Baseline of 3 is appropriate since the schema carries the weight.

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 opens with a clear verb-resource pair: 'Fetch one web page through the stealth browser and return clean, grounded content with provenance.' It also explicitly differentiates itself from siblings by stating when to use `search` or `research` instead, making the tool's scope unambiguous.

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?

The description provides explicit usage guidance: 'Reads a URL you already have: use `search` to find URLs, or `research` to search and read in one call.' It also mentions rate limiting per domain, giving the agent a concrete sense of when this tool is appropriate and what constraints apply.

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