Skip to main content
Glama

Site extract lite

site_extract_lite
Read-onlyIdempotent

Render up to 5 pages of one website in headless Chrome as clean text, obeying robots.txt. $0.03 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
urlYesstarting http(s) URL
fullNoset "1" for full crawl on paid calls
pagesNo1-5 (default 5)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover safety (readOnly, idempotent, non-destructive, openWorld), while the description adds real behavioral context the annotations cannot: headless Chrome rendering, robots.txt compliance, a $0.03 per-call price across named chains, and a two-phase wallet-signed payment handshake. It does not describe what happens when robots.txt blocks the URL or when payment validation fails, which is the remaining gap for a paid mutation-of-wallet-state tool.

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?

Three sentences, front-loaded with capability and scope before pricing and the payment procedure. The pricing sentence is dense with chain names but every element is decision-relevant for a paying caller; no filler.

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?

For a paid, robots-aware crawler with no output schema, the description covers output form ("clean text"), scope, cost, and the payment handshake, which is enough to invoke correctly. It leaves the shape of a multi-page result and the interaction between `full` and `pages` unspecified.

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 coverage is 100%, so the baseline is 3. The description adds genuine meaning for `payment` by explaining the sign-then-resubmit flow beyond the schema's PAYMENT-SIGNATURE note, but it never mentions `full` ("full crawl on paid calls"), leaving an ambiguity about whether that mode overrides the 5-page cap.

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?

The description gives a concrete verb and resource plus hard scope limits: "Render up to 5 pages of one website in headless Chrome as clean text, obeying robots.txt." The page cap and single-site restriction implicitly separate it from broader crawl or single-page siblings, but no sibling is named, so the differentiation is inferential rather than explicit.

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 payment procedure is spelled out step by step: call once without `payment` to obtain terms, sign with your own wallet, then call again with `payment`. That is clear operational guidance for the main non-obvious workflow. It stops short of saying when to prefer this over site_extract or page_extract, so no explicit alternative routing is provided.

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