Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

text_anagram_generator

Read-only

Generate anagrams from any text by rearranging its letters. Returns all permutations for inputs up to 8 characters, random shuffles for longer, with statistics and frequency map.

Instructions

Anagram Generator. Rearrange the letters of the supplied text into anagrams and return them with per-anagram length/is-original flags, summary statistics, and a character-frequency map. Input is cleaned to letters and digits only (punctuation/spaces removed) before permuting. For 8 or fewer cleaned characters it enumerates every distinct permutation deterministically; for longer input it emits random shuffles, so results vary between calls and are not idempotent. Operates only on the input's own letters — it does not consult a dictionary or wordlist, so outputs are letter rearrangements, not real words; for palindrome detection use text_palindrome_checker and for shuffling words/lines use text_randomizer. Pure local compute: read-only, non-destructive, offline, and rate-limited (60 requests/min for anonymous callers). Returns the anagram list, counts, and character frequencies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesSource text to rearrange; cleaned to letters/digits before permuting. Required and non-empty.
maxResultsNoMaximum number of anagrams to return. Clamped into 1-1000.
minLengthNoMinimum length an anagram must have to be included; also the minimum cleaned-text length (shorter input is rejected with 400). Clamped into 1-50.
includeOriginalNoWhen true the original (unshuffled) arrangement may appear in results; when false it is excluded.
caseSensitiveNoWhen false the cleaned text is lowercased before permuting; when true case is preserved.
sortByNoOrdering of the returned anagrams. length sorts longest-first; any other value sorts alphabetically.alphabetical

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoAlways true on success.
resultNoAnagram results and derived statistics.
optionsNoThe effective parameters after clamping/normalization.
Behavior5/5

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

Describes behavioral traits beyond annotations: deterministic for ≤8 chars, random for longer, input cleaning, offline/rate-limiting, and that outputs are not real words. 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?

One dense paragraph covering all key aspects without redundancy. Could be slightly more structured (e.g., bullet points) but all information is necessary and front-loaded.

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 output schema present, no need to detail return values. The description covers input cleaning, deterministic vs random behavior, dictionary absence, alternatives, and constraints (rate limit, offline).

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 has 100% coverage with descriptions. The description adds overall context but does not significantly augment individual parameter semantics beyond what schema already provides.

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 it generates anagrams by rearranging letters, lists return items (flags, stats, frequency map), and distinguishes from sibling tools like text_palindrome_checker and text_randomizer.

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 (anagram generation) and when not to (palindrome detection, word/line shuffling), naming specific alternatives. Also clarifies it does not use a dictionary.

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