John's Essentials

analyze_readability

Read-only

Readability Scorer — Calculate Flesch Reading Ease and Flesch-Kincaid Grade Level for a text. [category: analyze]

Input Schema

TableJSON Schema

Name	Required	Description	Default
`file`	No	Alternative: upload a .txt, .pdf, or .docx document (max 25MB).
`text`	No	Paste the text to score — about five words minimum. Leave blank if you are uploading a document instead.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026
- addedInput schema / properties / text / x-ui
```
Added value: +{
+  "multiline": true
+}
```
Changed1 schema field changedSep 25, 2026
- addedInput schema / x-require-one-of
```
Added value: +[
+  [
+    "file"
+  ],
+  [
+    "text"
+  ]
+]
```

Changed3 schema fields changedSep 11, 2026

changedInput schema / properties / text / description

Previous value: -"Plain text to score — minimum ~5 words. Required unless 'file' is provided."New value: +"Paste the text to score — about five words minimum. Leave blank if you are uploading a document instead."

addedInput schema / properties / text / title
```
Added value: +"Text to score"
```

changedInput schema / required

Previous value: -[
-  "text"
-]New value: +[]

First observedSep 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, deterministic read operation. The description adds the specific metrics computed and the input constraints (five words minimum, 25MB max), which is useful context beyond the annotations. It does not describe output format or edge cases, but the annotations carry the safety profile.

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?

The description is a single, front-loaded sentence that names the tool, the metrics, and the input type. The '[category: analyze]' tag is a minor addition but does not hurt. Every word 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?

For a simple read-only scoring tool with a complete schema and safety annotations, the description is nearly complete. It could mention the output format (e.g., scores returned), but the absence is minor given the tool's simplicity and the annotations.

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 the schema already documents both parameters well. The description adds the 'five words minimum' constraint and the 25MB limit, which are not in the schema, but it does not need to add much more because the schema is complete.

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 states a specific verb ('Calculate') and resource ('Flesch Reading Ease and Flesch-Kincaid Grade Level for a text'), which clearly distinguishes it from the many sibling analyze_* tools. The title 'Readability Scorer' reinforces the purpose without being a tautology.

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?

The description implies when to use it: when a readability score is needed, and the schema clarifies the two input modes (paste text or upload a document). It does not explicitly name alternatives or exclusions, but among the analyze_* siblings, none overlap with readability scoring, so the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All John's Essentials tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?