Skip to main content
Glama

Htmlentities

by io.github.pipeworx-io

Recent Alerts

recent_alerts
Read-onlyIdempotent

Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed is also at GET registry.pipeworx.io/alerts.json for scripts and dashboards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoOptional — filter to one subscription type.
limitNoMax events to return (1-200, default 50).
sinceNoOptional ISO timestamp — return events fired_at >= this time.
mark_readNoFlag the returned events read in the same call (default false).
unread_onlyNoReturn only events where read_at is null (default false).

TDQS

A3.8/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, but the description states 'Set mark_read:true to flag returned events read,' which is a state-changing operation. This directly contradicts the read-only annotation, making the behavioral transparency score 1 per the contradiction rule.

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 a tight three-sentence block that front-loads the main purpose and packs in filter options, mark_read semantics, polling guidance, and an alternative endpoint. Every sentence contributes distinct information with no redundancy or filler.

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?

With no output schema, the description fulfills the burden by mentioning the key return fields (source, citation_uri, raw payload). It also covers filtering, stateful reads, and polling. It does not explain pagination or limit behavior, but the schema covers limit, and the tool is relatively simple.

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?

The schema already provides full descriptions for all 5 parameters (coverage 100%), so the baseline is 3. The description adds value by giving a concrete example for type ('sec_8k'), clarifying the effect of mark_read (only newer events on next call), and reinforcing the since parameter's ISO timestamp format.

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 opens with 'Pull fired events from your subscription feed,' which is a specific verb+resource statement that clearly distinguishes this tool from siblings like list_subscriptions. It also details the output contents (source, citation_uri, raw payload), making the purpose unambiguous.

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?

The description provides clear context on how to use the tool: filter by type and since, set mark_read for stateful reads, and notes that polling is acceptable. It also mentions an alternative endpoint for scripts/dashboards, but does not explicitly contrast with sibling tools or state when not to use it.

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

All Htmlentities toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta (currently identical), and ask_pipeworx_grounded share the same routing core, while bet_research, polymarket_edges, polymarket_arbitrage, and polymarket_fill_risk all target prediction-market edge detection. The descriptions are detailed, but an agent must read a lot of nuance to avoid selecting the wrong tool.

Naming Consistency3/5

All names are lowercase snake_case and readable, but the convention is mixed: verb_noun names like encode_html and resolve_entity sit alongside bare verbs like remember and forget, and noun-phrase names like entity_profile, recent_changes, and polymarket_fill_risk. The ask_pipeworx_* and polymarket_* families are internally consistent, but there is no single predictable pattern across the whole set.

Tool Count2/5

At 33 tools this exceeds the 25+ threshold for a heavy set. The bloat is especially noticeable because the server is named Htmlentities yet only encode_html and decode_html relate to that purpose; the rest are unrelated Pipeworx research, prediction-market, memory, and subscription utilities.

Completeness4/5

The Pipeworx surface is broadly complete: ask/grounded/deep_research/discover/suggest cover data access, entity_profile/compare_entities/recent_changes/validate_claim cover entity workflows, and subscriptions and memory have create/list/delete lifecycles. Minor gaps such as no update operation for subscriptions or memories are workable, and encode/decode fully covers the literal Htmlentities purpose.

Resources