Skip to main content
Glama

HTML escape/unescape

bursia_html_escape
Read-onlyIdempotent

Escape HTML special characters (& < > " ') so text is safe inside HTML, or unescape them. Returns the converted text. Pure computation, free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "bursia_html_escape"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoescape (default) or unescape.
textYesText to escape, or escaped HTML to unescape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / mode / description
      Added value: +"escape (default) or unescape."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "escape",
      +  "unescape"
      +]
    • addedInput schema / properties / text / description
      Added value: +"Text to escape, or escaped HTML to unescape."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful context beyond that: it confirms the tool returns converted text and is 'pure computation, free,' which reassures the agent there are no side effects or costs. It does not discuss edge cases, but the annotation bar is lower.

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?

Two short sentences with zero waste, front-loading the escaping behavior and then stating the unescape inverse. Every sentence earns its place.

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?

For a simple pure-computation tool with complete schema coverage and annotations covering safety and idempotency, the description provides enough context to call it correctly. No output schema exists, but the return value is stated as converted text.

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 description coverage is 100%, so the schema already documents both parameters including the mode enum and default. The description does not add syntax or format details beyond what the schema provides, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb (escape/unescape) and resource (HTML special characters), and even lists the characters handled. It clearly states the operation, though it does not explicitly contrast with siblings like bursia_url_encode or bursia_base64.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage by saying 'so text is safe inside HTML' and offers unescape as the inverse, but it gives no explicit guidance on when to choose this tool over URL encoding or base64 siblings. No exclusions or alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources