Skip to main content
Glama
Sign In

SmartTools

by io.github.9thShini
OverviewDiscussionsAdmin

HTML entity encode / decode

html_entities

Escape the five special HTML characters (optionally all non-ASCII) or decode named and numeric HTML entities back to text. Runs on smart-tools.xyz.

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": "html_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to encode, or HTML with entities to decode
localeNoLanguage for the source_url link (default en)
directionNoencode (default) or decode
encode_allNoWhen encoding, also convert every non-ASCII character to a numeric entity. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It accurately states the core transformation behavior (escapes five special characters, optionally all non-ASCII, and decodes named/numeric entities), but it does not cover edge cases like invalid entity handling or the exact output format.

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 core description is one concise sentence with a clear action focus. The second sentence, 'Runs on smart-tools.xyz,' is filler that does not aid an agent, preventing a perfect score, but the overall length is still appropriate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is straightforward and the schema fully documents parameters. The description covers the main behavior adequately, though there is no output schema and edge cases are not mentioned. For a simple text utility, this is reasonably complete but could mention defaults or invalid input handling.

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?

The input schema provides 100% coverage for all four parameters, including defaults and enums, so the description does not need to compensate. The only slight addition is the phrase 'optionally all non-ASCII,' which aligns with the existing encode_all parameter description.

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 uses specific verbs 'Escape' and 'decode' and clearly identifies the resource: HTML entities and the five special HTML characters. This distinguishes it from sibling tools like url_encoder and base64 by focusing on HTML entity handling.

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?

The description implies usage for HTML escaping/decoding but does not explicitly mention when to use it over alternatives or provide exclusion criteria. An agent can infer the intended use, but the guidance is implicit rather than explicit.

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

All SmartTools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources