OnlineCyberTools MCP (280+ filterable tools)

text_text_statistics

Read-onlyIdempotent

Compute comprehensive text statistics including character, word, sentence, paragraph counts, reading time, and readability scores for a full linguistic profile.

Instructions

Text Statistics Analyzer. Compute a comprehensive statistics report for one block of text: character, word, unique-word, sentence, paragraph and line counts; per-character-class breakdown; word-length distribution; estimated reading and speaking time at several speeds; and (optionally) readability scores (Flesch Reading Ease, Flesch-Kincaid grade, Gunning Fog, Coleman-Liau, Automated Readability) with grade-level interpretation. Use this for a full linguistic profile in one call; use text_word_frequency when you only need ranked word-occurrence counts, or text_text_counter for a plain character/word/line tally. Runs locally on the supplied text: read-only, non-destructive, contacts no external service, and is rate-limited. Returns a nested statistics object plus the echoed options.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	Yes	The text to analyze. Must be non-empty; a blank value returns a 400 error.
`includeReadability`	No	When true, include the statistics.readability block (Flesch, Gunning Fog, Coleman-Liau, ARI). Set false to skip the readability computation.
`includeSentiment`	No	Reserved flag echoed back under options.includeSentiment; no sentiment block is produced.

Output Schema

TableJSON Schema

Name	Required	Description
`success`	No	True when analysis succeeded.
`statistics`	No	Nested metrics grouped by category.
`options`	No	Echoed request options.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.5.1Jun 3, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

addedInput schema / properties

Added value: +{
+  "includeReadability": {
+    "default": true,
+    "description": "When true, include the statistics.readability block (Flesch, Gunning Fog, Coleman-Liau, ARI). Set false to skip the readability computation.",
+    "type": "boolean"
+  },
+  "includeSentiment": {
+    "default": false,
+    "description": "Reserved flag echoed back under options.includeSentiment; no sentiment block is produced.",
+    "type": "boolean"
+  },
+  "text": {
+    "description": "The text to analyze. Must be non-empty; a blank value returns a 400 error.",
+    "examples": [
+      "The quick brown fox jumps over the lazy dog."
+    ],
+    "minLength": 1,
+    "type": "string"
+  }
+}

addedInput schema / required
```
Added value: +[
+  "text"
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "options": {
+      "description": "Echoed request options.",
+      "properties": {
+        "includeReadability": {
+          "description": "Effective readability flag used.",
+          "type": "boolean"
+        },
+        "includeSentiment": {
+          "description": "Effective sentiment flag (echo only).",
+          "type": "boolean"
+        },
+        "textLength": {
+          "description": "UTF-8 length of the analyzed text.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "statistics": {
+      "description": "Nested metrics grouped by category.",
+      "properties": {
+        "advanced": {
+          "description": "Averages, lexical diversity, most-common words, longest/shortest word, word-length distribution.",
+          "type": "object"
+        },
+        "basic": {
+          "description": "Core counts.",
+          "properties": {
+            "characters": {
+              "description": "Total UTF-8 character count.",
+              "type": "integer"
+            },
+            "charactersWithoutSpaces": {
+              "description": "Characters excluding spaces.",
+              "type": "integer"
+            },
+            "charactersWithoutWhitespace": {
+              "description": "Characters excluding all whitespace.",
+              "type": "integer"
+            },
+            "lines": {
+              "description": "Total line count.",
+              "type": "integer"
+            },
+            "nonEmptyLines": {
+              "description": "Lines with non-whitespace content.",
+              "type": "integer"
+            },
+            "paragraphs": {
+              "description": "Non-empty paragraph count.",
+              "type": "integer"
+            },
+            "sentences": {
+              "description": "Sentence count (split on . ! ?).",
+              "type": "integer"
+            },
+            "uniqueWords": {
+              "description": "Distinct lowercased words.",
+              "type": "integer"
+            },
+            "words": {
+              "description": "Word count (A-Za-z runs).",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "characters": {
+          "description": "Per-class counts (letters, digits, spaces, punctuation, uppercase, lowercase, special) and most-common characters.",
+          "type": "object"
+        },
+        "readability": {
+          "description": "Present only when includeReadability is true. Flesch Reading Ease, Flesch-Kincaid grade, Gunning Fog, Coleman-Liau, Automated Readability, plus interpretation. Score fields are null when the text has no words/sentences.",
+          "type": "object"
+        },
+        "time": {
+          "description": "Reading and speaking time estimates at multiple WPM speeds (minutes, formatted, wpm).",
+          "type": "object"
+        },
+        "words": {
+          "description": "Word totals, average/shortest/longest length, and length-category buckets.",
+          "type": "object"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when analysis succeeded.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate read-only and non-destructive. Description additionally states it runs locally, contacts no external service, and is rate-limited. No contradictions.

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?

Single paragraph that front-loads main purpose and lists statistics clearly. Slightly long but every sentence adds value.

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?

Covers all essential aspects: input constraints, options, output as nested statistics object plus options. Given complexity, complete.

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 description adds value by specifying text non-empty requirement, defaults for includeReadability, and the echoed behavior of includeSentiment.

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 clearly states the tool computes comprehensive text statistics (character, word, sentence counts, readability, etc.) and distinguishes it from siblings text_word_frequency and text_text_counter with specific use cases.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool ('full linguistic profile in one call') and when not to (use text_word_frequency or text_text_counter for narrower needs). Also notes it's read-only and local.

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

Deploy Server