Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_text_trimmer

Read-onlyIdempotent

Trim whitespace and custom characters from each line of text. Options include leading, trailing, both, or all occurrences, with support for preserving indentation and dropping empty lines.

Instructions

Text Trimmer (Whitespace & Character Cleanup). Trim and clean text by removing whitespace or custom characters from each line, with options to strip leading/trailing/all-occurrence characters, drop blank lines, and preserve indentation. Use it to normalize whitespace and tidy formatting; use text_find_replace for pattern-based edits and text_duplicate_line_remover to dedupe lines. Runs locally on the text you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/min anonymous). Returns the trimmed text plus before/after statistics and a count of characters, spaces, lines, and empty lines removed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to trim. Processed line by line, split on newlines.
trimTypeNoWhere to trim on each line. both trims both ends (right-only when preserveIndentation is true); left/leading trims the start; right/trailing trims the end; all removes every occurrence of the trim characters anywhere in the line.both
trimWhitespaceNoInclude standard whitespace (space, tab, newline, CR, null, vtab) in the trim set.
trimEmptyLinesNoAlso drop lines that are empty or whitespace-only.
customCharactersNoExtra characters to trim, added to the whitespace set. If set and trimWhitespace is false, only these characters are trimmed.
preserveIndentationNoKeep leading indentation; for both/left trim types only trailing whitespace is affected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether trimming succeeded.
resultNoThe trimmed output text.
statsNoBefore/after statistics and change counts.
optionsNoEcho of the effective options used.
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds significant context: runs locally, no external service, rate-limited (60 req/min), returns trimmed text plus statistics. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose and key options. Every sentence earns its place with no fluff. Structure is clear and scannable.

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?

With 6 parameters fully described in schema, annotations covering safety and idempotency, and mention of output statistics, the description is complete enough for effective tool 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 coverage is 100%, so baseline is 3. Description summarizes options but does not add new meaning beyond what the schema field descriptions already provide. No deeper explanation of parameter interactions.

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 title and description clearly state it trims whitespace and custom characters, with detailed options. It distinguishes from siblings like text_find_replace and text_duplicate_line_remover, making the purpose unambiguous.

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 says when to use (normalize whitespace/tidy formatting) and when not (pattern-based edits and duplicate line removal), naming alternative tools. This provides clear 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