Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

html_entities

Escape text to HTML entities or decode entities back to plain text and Unicode. Pure CPU, instant. Use to sanitise output or read scraped text.

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 escape or unescape
decodeNoDecode entities

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / decode
      Added value: +{
+  "description": "Decode entities",
+  "type": "boolean"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "description": "Text to escape or unescape",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "text"
+]
  4. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden; "Pure CPU, instant" usefully signals no network, no side effects, and low latency. It does not say whether decode is lenient on malformed or unknown entities, whether encoding is idempotent, or how invalid input is handled, which are the remaining behavioral questions for a transform tool.

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 no filler: the capability (both directions) is front-loaded and the usage hint follows. Every clause carries information, and there is no repetition of the tool name or padding.

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?

For a two-parameter, side-effect-free string transform with full schema coverage and no output schema needed (the return is obviously a string), the definition covers purpose, both modes, and usage. It is only marginally short on edge-case behavior for invalid entities, which is a minor gap at this complexity level.

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 both parameters (text, decode) are already documented in structured form, setting the baseline at 3. The description's mention of decoding maps onto the decode flag but adds no format, default-value, or edge-case detail beyond the 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?

States a specific verb and resource ("Escape text to HTML entities or decode entities back to plain text and Unicode") and covers both operating directions, so an agent can distinguish it from adjacent siblings like url_encode, base64, or entity_count without opening the schema.

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

Usage Guidelines4/5

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

"Use to sanitise output or read scraped text" gives a clear positive trigger for both modes (encode for output sanitisation, decode for scraped text), which is more than most utility definitions offer. It stops short of naming alternatives or exclusions (e.g., when to prefer url_encode or a full HTML parser), so it is clear context without routing.

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

All GadgetHumans API Hub 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