Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_html_entity_reference

Read-onlyIdempotent

Look up HTML character entities by name, glyph, or code. Search and filter a table of named entities with details like decimal and hex codes, description, and category.

Instructions

HTML Entity Reference Lookup. Search and filter a built-in table of named HTML character entities, returning each match as its entity name, decimal code, hex code, rendered glyph, plain-English description, and category (punctuation, math, currency, arrows, accents, greek, misc). Use this to look up the entity for a symbol or vice versa; use encoding_decoding_html_entities to actually encode or decode text into entities, text_ascii_table for plain ASCII codes, or webdev_http_status_reference for HTTP status codes. Runs locally on the static table: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests per minute for anonymous callers). Returns the paginated matching entities plus a fixed list of the most common entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoCase-insensitive substring matched against each entity name, glyph, description, decimal code, and hex code. Blank returns all entities (subject to the category filter).
categoryNoRestrict results to one category. Blank returns every category.
pageNoPage number for pagination over the filtered results (clamped to a minimum of 1).
itemsPerPageNoNumber of entities returned per page (clamped to a minimum of 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoWhether the lookup succeeded.
queryNoThe trimmed search query that was applied.
categoryNoThe trimmed category filter that was applied (empty when unfiltered).
pageNoThe page number returned.
itemsPerPageNoThe page size that was applied.
totalNoTotal number of entities matching the query and category before pagination.
totalPagesNoTotal page count for the current filter and page size.
entitiesNoThe matching entities for the requested page.
commonEntitiesNoFixed quick-reference list of the eight most common entities (lt, gt, amp, quot, nbsp, copy, reg, trade), independent of the query.
Behavior5/5

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

Beyond annotations (readOnlyHint=true, destructiveHint=false), the description adds concrete behavioral details: runs locally on a static table, no external service contact, rate-limited to 60 req/min for anonymous callers. No contradiction with annotations.

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?

The description is concise (4 sentences) and well-structured: purpose first, then usage guidance, then behavioral details. Every sentence adds value with no redundancy.

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 existence of an output schema (not shown), the description covers purpose, usage guidance, behavioral traits, and even extra detail like the fixed list of common entities. It is fully adequate for an AI agent.

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 detailed parameter descriptions. The description adds context not in the schema, such as 'Blank returns all entities' and mentions pagination pattern, but does not significantly extend parameter semantics.

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 the tool's purpose as an HTML entity reference lookup, specifying the exact fields returned (entity name, decimal code, hex code, rendered glyph, description, category). It explicitly distinguishes from sibling tools like encoding_decoding_html_entities, text_ascii_table, and webdev_http_status_reference.

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 provides explicit guidance: 'Use this to look up the entity for a symbol or vice versa; use encoding_decoding_html_entities to actually encode or decode...'. It also mentions operational constraints (local, rate-limited).

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