Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_counter

Read-onlyIdempotent

Count characters, words, lines, sentences, and paragraphs in a text block. Get reading time estimates and top frequent characters for quick analysis.

Instructions

Text Counter (character, word, and line tally). Count the characters, characters-without-spaces, words, lines, sentences and paragraphs of one block of text, plus average characters-per-word and words-per-sentence, an estimated reading time at three speeds, and (when the text exceeds 10 words) the ten most frequent a-z/space characters. Use this for a quick plain tally; use text_text_statistics instead for a richer linguistic profile with readability scores, or text_line_counter when you only need line counts and line-length metrics. Runs locally on the supplied text: read-only, non-destructive, contacts no external service, and is rate-limited. Returns a stats object, a readingTime object, and a topCharacters map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to count. May be empty; an empty string yields zero counts. Counting is Unicode code-point based; lines split on newlines, sentences split on runs of . ! ?, paragraphs split on blank lines.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when counting succeeded.
statsNoCore counts and averages.
readingTimeNoEstimated reading time strings (e.g. 30 sec, 2 min).
topCharactersNoMap of the up-to-10 most frequent a-z/space characters to their counts. Empty object when the text has 10 or fewer words.
Behavior5/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. Description adds that it runs locally, is non-destructive, contacts no external service, and is rate-limited. No contradiction.

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?

Description is concise yet thorough, front-loads core functionality, lists metrics, then gives usage guidelines and behavioral notes. Every sentence is valuable.

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?

For a simple one-parameter tool with output schema present, the description covers all essential aspects: what it counts, usage guidance, behavior, and return structure. No gaps.

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

Parameters5/5

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

Schema description coverage is 100%; the description adds meaning about empty strings yielding zero counts, Unicode code-point based counting, and how lines, sentences, paragraphs are split.

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 it counts characters, words, lines, sentences, paragraphs, averages, reading time, and top characters. It distinguishes itself by naming alternatives like text_text_statistics and text_line_counter.

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 states when to use this tool (quick plain tally) and when to use alternatives (text_text_statistics for richer linguistic profile, text_line_counter for just line counts).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server