Skip to main content
Glama

Score readability with Flesch, Fog and SMOG

text_readability
Read-only

Readability of a text in pure code: Flesch Reading Ease, Flesch-Kincaid grade, Gunning Fog, SMOG, Coleman-Liau and ARI, with counts of characters, words, sentences, syllables and complex words, and reading and speaking time. English formulas; other languages get counts only. Syllables are counted by a vowel-group heuristic, so scores are estimates. Up to 100 KB. Related tools on this server, for a different need: text_answer when you need answers a question from the given text only; text_chunk when you need to generate overlapping text chunks with character offsets. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "text": "<text>"
    },
    "name": "text_readability"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe text, up to 100 KB (JSON body field)
languageNoen (default: all formulas); other codes return counts and times only

Output Schema

NameRequiredDescriptionDefault
countsNo
scoresNo
sourceNo
languageNo
checkedAtNo
readingMinutesNo
speakingMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations it discloses genuinely decision-relevant behavior: a hard 100 KB limit, the accuracy caveat that syllables come from a vowel-group heuristic so scores are estimates, the language restriction (English formulas only), and a per-call price of $0.002 charged via x402 with failed calls free. That pricing and failure-charging detail is exactly the kind of context annotations cannot express.

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 metric list and the accuracy/limit caveats are front-loaded in a single dense sentence pair, with routing and pricing in trailing sentences. It is well structured and mostly earns its length, though the payment sentence is verbose about networks and could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, yet the description still summarizes what comes back. Combined with the size limit, language behavior, accuracy caveat, and cost model, an agent has everything needed to call this correctly and to know whether the result should be trusted as exact or estimated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters and the baseline is 3. The description still adds real meaning by explaining the consequence of the language field ('other languages get counts only') and by tying the text parameter to the 100 KB ceiling, which the schema states but the description reinforces behaviorally.

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?

The description names a specific verb ('Readability of a text') and enumerates the exact outputs (Flesch Reading Ease, Flesch-Kincaid, Gunning Fog, SMOG, Coleman-Liau, ARI, plus counts and reading/speaking time), so an agent knows precisely what it produces. It also explicitly separates itself from text_answer and text_chunk, preventing confusion with sibling tools.

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?

It gives concrete routing rules: use text_answer when you need answers grounded in the text, and text_chunk when you need overlapping chunks with offsets. That is explicit guidance for the main confusable alternatives, though it stops short of stating when this tool should NOT be used (e.g. for non-English scoring beyond counts).

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