Skip to main content
Glama

Text statistics for a web page's visible content

text_stats
Read-only

Text statistics for a web page's visible content: word, sentence and paragraph counts, reading time, Flesch reading-ease score and top keywords (stop words removed). Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description goes further by disclosing latency (1-3 s), a hard quota (20 calls/day per user across free tools), and the paid overage path via x402/USDC on Base. It doesn't mention that the target page must be publicly reachable, but the schema's 'Public http(s) URL' covers that.

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

Conciseness5/5

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

One dense sentence front-loads purpose and outputs, followed by two short sentences on speed and cost. No filler, and the commercially important constraint (free quota, then price) is placed last where it doesn't obscure the function.

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 naming every reported metric. Payment, rate limits and latency are covered; only minor details such as how many keywords are returned or whether counts cover the whole page are left open.

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 payment are already fully documented in the schema, including the x402 payment-signature flow. The description's pricing sentence is consistent with the payment parameter but adds no new semantics about how to pass it. Baseline 3 applies.

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 specific resource (a web page's visible content) and enumerates exactly what is computed: word, sentence and paragraph counts, reading time, Flesch score, top keywords. The 'statistics' framing also separates it from extraction siblings like page_text and page_markdown without naming them.

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 context is implied by the enumerated metrics (readability/content analysis) but there is no explicit when-to-use, when-not-to-use, or named alternative among the many page-content siblings. The free-tier and per-call price give a reason to be economical, not a reason to pick this tool over another.

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.