Skip to main content
Glama

agent-exec

Read one web page as text (paid, x402)

scrape_page
Read-only

PAID: scrape a web page: readable text, title, links and meta for $0.0100. We fetch it (public URLs, up to 2000000 bytes). Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scrape_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe absolute http(s) URL of the page, e.g. https://example.com/.
maxCharsNoLower the text cap: 1..40000. Omitted means 40000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare read-only/non-destructive; the description adds the things an agent actually needs: the $0.0100 cost, the 2,000,000-byte fetch limit, the fact that the first call is a price discovery round-trip, the accepted chains and asset (USDC), and where the payment must be placed in _meta. That is substantial behavioral context beyond the structured fields.

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-loaded with the paid nature, price and payload, then the mechanics, which is the right order for an agent deciding whether to spend. The trailing feedback/"Read daily; no individual reply" sentences are somewhat cryptic and the payment-chain list bulks up the middle, but overall little is wasted.

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 only two fully documented parameters and no output schema, the description usefully substitutes for the missing output schema by naming the returned fields (text, title, links, meta). It leaves error/refund behavior and whether the first unpaid call is itself billed unstated, which matters for a paid tool.

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 both url and maxChars are already documented with ranges. The description adds only the constraint that URLs must be public and the byte-level fetch cap, which is related but does not explain maxChars truncation behavior, so it stays at the schema-does-the-work baseline.

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 opens with a specific verb and resource ("scrape a web page") and enumerates the returned payload (readable text, title, links, meta) plus the price. It never names a sibling such as doc_text, so an agent has no explicit signal about which reader to pick when both could apply.

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?

Operational guidance is clear: an unpaid call returns the price, then the agent must attach an x402 payment in _meta['x402/payment'] and call again. That is a concrete when/how-to-call sequence, but there is no explicit exclusion or comparison against alternative read tools, so it stops short of a 5.

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.