Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_unicode

Read-onlyIdempotent

Escape text into Unicode escape sequences or decode them back to characters, supporting JSON, Python, Java, CSS, HTML, XML, and URL formats. Runs locally without external services.

Instructions

Unicode Escaper and Unescaper. Escape text into Unicode escape sequences, or unescape them back to characters, in JSON/JavaScript, Python, Java, CSS, HTML, XML, or URL format. Set operation to escape or unescape and format to the target syntax. Encodes non-ASCII and control characters as backslash-uXXXX (json/java), backslash-uXXXX or backslash-UXXXXXXXX (python), backslash-XXXXXX (css), hex numeric HTML entities, decimal numeric XML entities, or percent-XX UTF-8 bytes (url), handling surrogate pairs and astral code points. Unescape auto-detects and decodes every one of these sequence styles at once, so format only affects escape. Use encoding_decoding_html_entities for named HTML entities, encoding_decoding_punycode for IDN domain names, conversion_emoji to look emoji up by name/codepoint, and encoding_decoding_string_escape for SQL/CSV/JavaScript string quoting. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonym

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesInput to convert: plaintext when escaping, or a string containing Unicode escape sequences when unescaping. Must not be blank.
operationYesDirection: escape converts characters to escape sequences; unescape decodes escape sequences back to characters.
formatNoTarget escape syntax used when escaping (unescape auto-detects all styles): json/java use backslash-uXXXX, python adds backslash-UXXXXXXXX for astral, css uses backslash-XXXXXX space-terminated, html uses hex numeric entities, xml uses decimal numeric entities, url uses percent-XX UTF-8 bytes. Defaults to json.json

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the conversion succeeded.
inputNoThe submitted text, echoed back.
operationNoThe operation performed (escape or unescape).
formatNoThe effective format after defaulting (json when omitted).
resultNoThe escaped string (escape) or decoded text (unescape).
format_infoNoMetadata describing the chosen format.
analysisNoCharacter and code-point statistics for the input text.
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds: 'Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute...' It also mentions handling surrogate pairs and astral code points. While it doesn't explain error handling, it adds sufficient operational context.

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 medium paragraph with front-loaded purpose, then operation/format details, then unescape auto-detection, then sibling alternatives, and finally local execution/rate limit. It is mostly concise, though could be slightly more structured (e.g., bullet points). Every sentence adds value.

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 the tool has 3 parameters, 100% schema coverage, annotations, and an output schema, the description covers all needed aspects: what it does, how to set operation and format, unescape auto-detection, sibling alternatives, and local/rate-limited behavior. No critical gaps remain for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with each parameter described. The description adds extra meaning for the 'format' parameter by detailing each syntax (e.g., 'json/java use backslash-uXXXX, python adds backslash-UXXXXXXXX for astral'). This goes beyond the schema's brief enum labels.

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's a Unicode Escaper and Unescaper, specifying escape targets (JSON, Python, Java, CSS, HTML, XML, URL) and distinguishing itself from sibling tools like encoding_decoding_html_entities and conversion_emoji. The verb 'Escape/Unescape' and resource 'text into Unicode escape sequences' are specific and unique.

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 explicitly tells when to use this tool (escape/unescape Unicode) and when not to use it, naming alternatives: 'Use encoding_decoding_html_entities for named HTML entities, encoding_decoding_punycode for IDN domain names...' This provides clear guidance on tool selection.

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