Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_line_counter

Read-onlyIdempotent

Count and analyze text lines: returns total, non-empty, blank lines, line-length statistics, length distribution, and optional line numbering.

Instructions

Count And Analyze Text Lines. Count and measure the lines of a text block: returns total lines, non-empty lines, blank lines, and line-length stats (max/min/average length plus the 1-based line numbers of the longest and shortest lines) and a length-bucket distribution. Optionally returns the text with line numbers prepended. Use this for line-focused metrics; use text_counter or text_text_statistics for word, character, sentence, and readability metrics, or text_sort_lines to reorder lines. It does NOT deduplicate or detect duplicate/unique lines. Pure local compute: read-only, non-destructive, offline, rate-limited (60 requests/minute for anonymous callers). Returns a stats object, an optional numberedText string, and a lengthDistribution array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to analyze; split into lines on newline. Empty input yields zeroed stats.
showLineNumbersNoWhen true, numberedText prepends a right-padded line number (e.g. " 1: line") to each line; otherwise numberedText echoes the input unchanged.
skipBlankLinesNoWhen true (and showLineNumbers is true), blank/whitespace-only lines are emitted verbatim and not assigned a number. Does not affect the stats counts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on success.
statsNoLine metrics for the input.
numberedTextNoInput with line numbers prepended when showLineNumbers is true; otherwise the input verbatim. Empty for empty input.
lengthDistributionNoLine-length buckets (0-20, 21-50, 51-80, 81-120, 120+); empty buckets omitted.
optionsNoEcho of the effective request options.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds that it is 'pure local compute: read-only, non-destructive, offline, rate-limited (60 requests/minute)'. It also handles edge cases like empty input yielding zeroed stats, and explains the behavior of showLineNumbers and skipBlankLines parameters.

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 well-structured, starting with the core purpose, followed by outputs, usage guidance, limitations, and non-functional properties. It is efficient and every sentence adds value without redundancy.

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?

Given the tool's complexity (3 parameters, output schema exists), the description covers all necessary aspects: input handling, output details, rate limits, safety profile, and comparisons to siblings. It is complete for agent selection and invocation.

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 baseline is 3. The description adds minimal extra per-parameter detail beyond the schema; it reiterates parameter effects but doesn't provide additional semantic meaning for the parameters. It does mention edge cases like empty input, which is slightly beyond schema.

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 that the tool counts and analyzes text lines, providing specific metrics like total lines, non-empty lines, blank lines, line-length stats, and line numbers. It also distinguishes itself from sibling tools by naming alternatives (text_counter, text_text_statistics, text_sort_lines) and explaining what it does not do (deduplication).

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?

Explicit guidance is given: 'Use this for line-focused metrics; use text_counter or text_text_statistics for word, character, sentence, and readability metrics, or text_sort_lines to reorder lines.' It also clarifies that it does not deduplicate, helping the agent decide when to use this tool.

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