Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_text_joiner

Read-onlyIdempotent

Join an array or newline-separated text elements into one string with custom separators and structured output formats (CSV, JSON, HTML, etc.). Optionally trim, deduplicate, sort, or add prefixes/suffixes.

Instructions

Text Joiner. Join an array (or newline-separated string) of text elements into one string using a chosen separator, with optional trim, deduplicate, sort, prefix/suffix, drop-empty, and a structured output format (plain, csv, json, html-list, xml, numbered, bulleted, quoted, sql-values). Use this to merge lines/items; use text_splitter for the inverse (breaking one string into parts). Pure local compute: read-only, non-destructive, offline, and rate-limited (60 requests/min for anonymous callers). Returns the joined result plus element/length statistics and the effective settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementsYesItems to join: an array of strings, or a single string that is split on newlines (blank lines dropped).
separatorNoString inserted between elements (ignored by csv/json/xml/html-list/sql-values formats, which use their own delimiters).
formatNoOutput structure. text joins with separator; others emit CSV row, JSON array, HTML/XML list, numbered/bulleted/quoted lines, or a SQL VALUES tuple.text
removeEmptyNoDrop elements that are empty or whitespace-only before joining.
trimElementsNoTrim leading/trailing whitespace from each element.
addPrefixNoString prepended to every element after trim/sort.
addSuffixNoString appended to every element after trim/sort.
sortNoLexicographically sort elements before joining.
sortDirectionNoSort order when sort is true.asc
uniqueNoRemove duplicate elements, keeping first occurrence.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on success.
resultNoThe joined output string in the chosen format.
statsNoMetrics over the processed elements.
settingsNoEffective options applied: separator, format, removeEmpty, trimElements, addPrefix, addSuffix, sort, sortDirection, unique.
Behavior5/5

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds that it is pure local compute, offline, rate-limited (60/min for anonymous), and explains the return value structure (joined result + statistics + settings). This goes beyond 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 a single paragraph that efficiently covers purpose, usage, options, and behavior. It is front-loaded with the main action. Slightly verbose in listing all formats, but that detail is useful for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists (not shown) and schema coverage is 100%, the description is sufficiently complete. It mentions return value components and contrasts with a sibling tool. It could mention the default separator or output format more explicitly, but overall adequate.

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 descriptions for each parameter. The description does not add new semantic meaning beyond what's in the schema, but it provides a readable overview. Baseline of 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 explicitly states the tool joins text elements into one string with configurable formatting. It names the core action (join) and resource (text elements), and distinguishes from the sibling tool text_splitter, providing clear differentiation.

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?

The description directly tells when to use this tool ('merge lines/items') and when not to, by pointing to text_splitter as the inverse. It includes explicit guidance on usage context.

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