Skip to main content
Glama

Agent safety checks: prompt-injection scan, honeypot check, x402 preflight + crypto data (USDC/x402)

Read any URL as clean, injection-scrubbed Markdown for an LLM

stealth_read
Read-only

Read a public https page for an agent: the main content as clean Markdown (headings, lists, tables kept; navigation, cookie banners, scripts and everything hidden from humans removed), scrubbed by the input guard — instructions aimed at the model replaced, invisible Unicode stripped — with verdict, score, findings, title and language. JSON and text pass through. One GET as a declared bot, no login or bot-protection bypass; a blocked page is never charged. 0.02 USDC base (new payers 0.02, >10 payments 0.014; 1 pack call). After: preflight before your agent buys or pays anything the page offers (the result's next field has the exact call).

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

Input Schema

NameRequiredDescriptionDefault
urlYesthe public https page to read (1 MB, 10 s)
payment_txNoHash of a USDC transfer on Base to payTo (≥ the price, ≤ 72 h old) instead of an x402 signature.
bundle_tokenNoToken from buy_signal_pack, buy_subscription (pro/desk) or buy_enterprise instead of paying per call.
payer_addressNoWallet you pay from: the payment-required error quotes your tier (0 payments base price (new-payer surcharge paused), 1-10 base, >10 -30 %) and, from the third payment, an upgrade with your own spend.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real substance beyond them: one GET as a declared bot, no login or bot-protection bypass, blocked pages never charged, and a full price schedule including the pack-call accounting. However, it never states rate limits, retry behavior, or failure modes beyond "blocked", so a 3 rather than a 5.

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?

The most important information — what is fetched and what is returned — is front-loaded in the first sentence, and the workflow hint is placed last. The middle is dense with nested parentheses and pricing minutiae, which slows parsing but is not filler for a paid tool.

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?

For a tool with no output schema, the description still enumerates the return shape (verdict, score, findings, title, language, plus a next field). Combined with the documented size/time limits and the payment paths, an agent has everything needed to call it correctly and interpret the result.

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 baseline is 3; the description adds only the payment model context (0.02 USDC base, 0.014 after 10 payments, 1 pack call) that clarifies why payer_address and bundle_token exist. It does not explain the interaction between payment_tx and bundle_token precedence or what happens if both are supplied.

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 first clause names a specific verb and resource ("Read a public https page for an agent") and immediately specifies the output form ("main content as clean Markdown"), including what is kept and what is stripped. It is clearly distinguishable from siblings like input_guard (scrubbing engine) or preflight (purchase check) because it is the fetch step that feeds them.

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?

The trailing sentence gives an explicit sequencing rule: read the page first, then run preflight before buying anything the page offers, and notes the result's next field carries the exact call. It does not name a when-not-to-use case or an alternative fetch tool, but the workflow context is concrete rather than implied.

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