Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_add_prefix_suffix

Read-onlyIdempotent

Add a fixed prefix and/or suffix to every line, word, or character of text. Use for wrapping, indenting, quoting, or tagging multiple elements at once.

Instructions

Add Prefix And Suffix To Text. Add a prefix string, a suffix string, or both around every line, every word, or every character of the supplied text, choosing the granularity with targetType (lines, words, or characters). Use text_add_prefix_suffix to wrap, indent, comment out, quote, or tag many elements at once; use text_add_line_numbers instead when you need sequential numbering rather than a fixed repeated affix, and text_joiner when you need to concatenate separate elements with a separator. 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 transformed string plus before/after statistics and the effective options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to transform. Must not be blank; a blank value returns a 400 error.
prefixNoString prepended to each target element. Empty string adds no prefix.
suffixNoString appended to each target element. Empty string adds no suffix.
targetTypeNoGranularity of the affix. lines wraps each newline-separated line, words wraps each whitespace-separated word (whitespace preserved), characters wraps each character. Any other value returns the text unchanged.lines
skipEmptyNoWhen true, blank lines or words are left untouched. Ignored for the characters target.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the transformation succeeded.
resultNoThe transformed text with prefixes and/or suffixes applied.
statsNoBefore and after counts plus a record of what changed.
optionsNoThe effective options after defaults were applied.
Behavior5/5

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

Annotations already declare readOnly=true, destructive=false, idempotent=true. Description adds specific rate limit (60 req/min for anonymous), confirms local execution, no external service, and describes return value (transformed string plus stats and effective options).

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 pack essential info: purpose, use cases, behavior, and output. No fluff, front-loaded with the core action.

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 params, 100% schema coverage, annotations, and an output schema (implied by description mentioning stats), the description covers all needed context: what tool does, how to choose granularity, guidance vs siblings, safety/limits, and return structure.

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 covers all 5 parameters with 100% description coverage, so baseline is 3. Description mentions targetType and implies use cases for affixes but does not add new parameter-level details 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 starts with a clear action 'Add Prefix And Suffix To Text' and specifies the granularity options (lines, words, characters). It names exact siblings (text_add_line_numbers, text_joiner) to distinguish this tool's purpose of wrapping elements with fixed affixes.

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 (wrap, indent, comment out, quote, tag) and when to use alternatives (sequential numbering -> text_add_line_numbers, concatenate with separator -> text_joiner). Also notes it runs locally, is read-only, and rate-limited.

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