Skip to main content
Glama

Prompt Sanitizer — prompt-injection scan for untrusted content

Read any public page as clean Markdown, with hidden text removed

stealth_read
Read-only

Returns a public https page as clean Markdown for an agent (headings, lists, tables kept; navigation, cookie banners, scripts and everything hidden from people removed), strips invisible Unicode and flags text aimed at the model — 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. Free with a key (500 calls) or 5 calls a day without one; then 0.02 USDC per call via x402, or 1 call from a key. 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_tokenNoYour key instead of paying per call: free (500 calls, POST /key) or bought by card. The connection header X-Bundle-Token works too.
payer_addressNoWallet you pay from (optional; the x402 price is the same for every address).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / bundle_token / description
      Previous value: -"Token from buy_signal_pack or buy_pack_with_card instead of paying per call."New value: +"Your key instead of paying per call: free (500 calls, POST /key) or bought by card. The connection header X-Bundle-Token works too."
    • changedInput schema / properties / payer_address / description
      Previous value: -"Wallet 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."New value: +"Wallet you pay from (optional; the x402 price is the same for every address)."
  2. Changed1 schema field changed
    • changedInput schema / properties / bundle_token / description
      Previous value: -"Token from buy_signal_pack, buy_subscription (pro/desk) or buy_enterprise instead of paying per call."New value: +"Token from buy_signal_pack or buy_pack_with_card instead of paying per call."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, yet the description adds substantial behavior: hidden text and invisible Unicode removal, prompt-injection flagging with verdict/score/findings, JSON/text passthrough, one declared-bot GET with no bypass, and the fact that blocked pages are never charged. It also covers auth and billing paths, which matters for a tool that can incur per-call cost.

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?

Front-loads purpose and filtering behavior before pricing, which is the right order. The paragraph is dense and the trailing 'After:' sentence is terse to the point of being cryptic, but nearly every clause carries information an agent needs.

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?

No output schema exists, yet the description names the return fields (verdict, score, findings, title, language) and the passthrough cases. Combined with schema-level size and timeout limits, auth requirements, and pricing, nothing essential for correct invocation is missing.

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, but the description adds real meaning for the payment parameters by explaining the key-based free tier (500 calls), the no-key quota (5/day), and the x402 fallback at 0.02 USDC per call. That clarifies when payment_tx or bundle_token is actually needed, going beyond the field-level descriptions.

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 ('Returns a public https page as clean Markdown for an agent') and specifies what is preserved (headings, lists, tables) versus removed (navigation, cookie banners, scripts, hidden text). It also names the injection-flagging behavior, so it is clearly distinguishable from buy_pack_with_card and input_guard.

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 ('preflight before your agent buys or pays anything the page offers') and an explicit boundary (no login, no bot-protection bypass; only public https pages). It does not compare against the sibling tools by name, so the alternative-selection guidance is implicit rather than spelled out.

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.