Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_duplicate_line_remover

Read-onlyIdempotent

Remove duplicate lines from text while keeping the first occurrence. Options include case-sensitive matching, whitespace trimming, empty-line retention, and alphabetical sorting.

Instructions

Duplicate Line Remover. Remove duplicate LINES from text, keeping the first occurrence of each, with options for case-sensitive matching, whitespace trimming, empty-line handling, and alphabetical sorting of the result. Operates on whole lines split on newlines - use text_duplicate_word_remover to dedupe individual words, text_remove_duplicate_characters to dedupe characters, or text_sort_lines to only reorder lines without removing duplicates. Runs locally on the text you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the deduplicated text plus before/after line statistics and a top-10 list of the most repeated lines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoMulti-line text to deduplicate, split on newline. Blank input returns empty output with zeroed stats.
caseSensitiveNoWhen true, lines differing only in letter case are kept as distinct; when false (default), comparison is case-insensitive.
trimWhitespaceNoWhen true (default), leading/trailing whitespace is stripped before comparing and in output; when false, whitespace is significant.
keepEmptyLinesNoWhen true, blank lines are preserved and deduplicated; when false (default), all empty lines are dropped.
sortResultsNoWhen true, surviving unique lines are sorted alphabetically (case-aware per caseSensitive); when false (default), original order is preserved.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether deduplication succeeded.
resultNoThe deduplicated text, unique lines joined by newline.
statsNoBefore/after line counts and reduction metric.
duplicateAnalysisNoUp to 10 most-repeated lines, sorted by descending count.
optionsNoThe effective options after defaults were applied.
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds: runs locally, no external service, rate-limited (60 req/min), returns statistics and top-10 repeated lines. No contradiction with annotations.

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 description is well-structured but somewhat long; however, every sentence adds value including purpose, options, sibling differentiation, and safety. Could be slightly more concise but earns its length.

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 5 boolean parameters with defaults documented in schema, and existence of output schema (mentioned in description), the description covers purpose, behavior, alternatives, return structure, and constraints. Fully complete.

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 coverage is 100% with good descriptions. The description does not add new parameter details beyond summarizing options, but the schema already fully documents each parameter, so baseline 3 is appropriate.

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 removes duplicate lines from text, keeping first occurrences, with specific options. It distinguishes from siblings like word and character deduplication tools, meeting the 'specific verb+resource' criterion.

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 lists alternatives: text_duplicate_word_remover, text_remove_duplicate_characters, text_sort_lines. Also notes local execution, rate limits, and non-destructive nature, providing clear when-to-use and when-not-to-use guidance.

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