Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

encoding_decoding_html_entities

Read-onlyIdempotent

Encode special characters to HTML entities or decode entities back to characters to safely embed text in HTML/XML and prevent XSS attacks.

Instructions

Encode or Decode HTML Entities. Convert special characters to HTML entities and back so text is safe to embed in HTML/XML markup and to prevent XSS. Encoding replaces characters with named (<), decimal (<), or hex (<) entities; decoding resolves all three forms back to characters. Use this for HTML/XML markup safety; use encoding_decoding_url for URL percent-encoding, encoding_decoding_unicode for \u/\x source-code escapes, and encoding_decoding_string_escape for SQL/CSV/code string-literal quoting. Runs locally on the supplied text: read-only, non-destructive, offline, and rate-limited (60 requests/min anonymous). Returns the converted string plus a length and entity-count analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe text to encode or decode. Required, non-empty.
operationYesencode converts characters to HTML entities; decode resolves named/decimal/hex entities back to characters.
modeNoEncode only. safe escapes < > & " only; all also escapes every non-ASCII character; extended escapes the common Latin-1, punctuation, and currency ranges. Ignored when decoding.safe
formatNoEncode only. Output entity form: named (&lt; with numeric fallback), decimal (&#60;), or hex (&#x3C;). Ignored when decoding.named

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the operation succeeded.
inputNoThe original text, echoed back.
operationNoThe operation performed (encode or decode).
modeNoThe encode mode used (safe, all, or extended).
formatNoThe encode output format used (named, decimal, or hex).
resultNoThe encoded or decoded output string.
analysisNoLength and entity-count metrics for the conversion.
Behavior4/5

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description adds value by noting local execution, offline operation, rate limit (60/min), and return content analysis, exceeding what annotations provide.

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?

Single paragraph with clear structure: purpose, technical detail, usage guidance, operational notes. Efficient but could be slightly more concise; still well-organized.

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 full schema coverage and output schema existence, the description is comprehensive. Covers all parameters, usage context, behavioral notes, and return value analysis.

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?

With 100% schema coverage, the description still adds meaning by explaining operation, mode, format, and their defaults. Clarifies that mode/format are ignored when decoding, which is not in 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 clearly states 'Encode or Decode HTML Entities' and explains the conversion. It distinguishes from sibling tools by naming specific alternatives (URL, Unicode, string escape). The purpose is 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 states when to use (HTML/XML markup safety) and when not, listing three sibling tools with distinct purposes. This provides clear guidance for 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