Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Text statistics for a public web page

text_readability
Read-only

Readability score and word count of a web page. Fetch a public page (respects robots.txt) and return word count, sentence count, average sentence length, reading time (200 wpm) and a Flesch reading-ease score for its main text. No AI involved. Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/text/readability

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, yet the description adds genuinely useful operational context: robots.txt compliance, the absence of AI processing, and a per-call price of $0.001 USDC via x402 v2 on Base. It does not explain failure modes (e.g., non-HTML content, blocked pages) or output shape, but the cost and access constraints are valuable additions beyond the annotations.

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 core purpose and returned metrics are front-loaded in the first two sentences, with cost and demo details trailing. The free-demo URL is slightly promotional, though it does give the agent a zero-cost way to validate the tool, so it broadly earns its place.

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, the description carries the return-value burden and does so by listing all metrics (word count, sentence count, average sentence length, reading time at 200 wpm, Flesch score) for the main text. What remains vague is how 'main text' is extracted from a page with navigation or boilerplate, and no failure behavior is described.

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?

With a single parameter at 100% schema coverage (format uri, maxLength 2048, 'Public http(s) URL'), the schema already carries the semantics. The description reinforces that the target must be publicly reachable and robots.txt-permitted, which slightly sharpens the constraint but adds little beyond the schema.

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 names a specific verb and resource (readability score and word count of a web page) and enumerates the exact metrics returned, so an agent knows precisely what it produces. It does not explicitly differentiate itself from siblings like text_keywords or web_markdown, leaving that to inference.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'Fetch a public page (respects robots.txt)' tells the agent only public pages are eligible, and 'No AI involved' signals a deterministic alternative to LLM-based reading. There is no explicit when-to-use/when-not or named alternative among the sibling tools.

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