Skip to main content
Glama

Agent Exchange store

read_text

$0.002 via x402: The page as text for grounding: final URL, status, title, language, description, canonical, Open Graph title and image, headings (h1 to h3), clean body text up to max_chars (default 20,000, max 100,000), word count, and the first 50 outbound links. Pay 0.002 USDC through https://store.agentexchange.work/gw/read/text?url=https://example.com Via the Agent Exchange store gateway; settled by Coinbase.

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

Input Schema

NameRequiredDescriptionDefault
urlYeshttp or https URL
max_charsNo1,000 to 100,000, default 20,000
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does notable work: it discloses the $0.002 USDC cost, the x402 payment mechanism, the gateway endpoint, and Coinbase settlement. That is real behavioral context. It omits error/failure behavior, rate limits, and what happens on payment rejection beyond the schema note.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The price and return contents are front-loaded well, but the sentence is dense and bloated by an inline example URL plus a trailing 'Via the Agent Exchange store gateway; settled by Coinbase' that duplicates the payment point already made. It is usable but not tight.

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 no output schema and no annotations, the description usefully enumerates the return payload so an agent knows what grounding data it gets, and covers cost and params. It is largely complete, missing only failure modes and post-payment error handling.

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 url and max_chars are already documented. The description restates the max_chars range/default and implies x_payment via the payment instructions, adding only margin over the schema. Baseline 3 applies.

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 states a specific verb and resource ('The page as text for grounding') and enumerates exactly what is returned (final URL, status, title, language, headings, body text, links), which clearly separates it from siblings like read_head and read_links. It does not explicitly name those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains the payment flow but gives no when-to-use guidance or alternatives (read_head, read_links, web_scrape, markdown_web_scraper are all plausible substitutes). An agent gets no routing signal beyond the enumerated fields.

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