Skip to main content
Glama

Htmlentities

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior. The description adds scoping details (anonymous IP, BYO key hash, account ID) and the listing behavior when key is omitted, providing context beyond 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?

Three focused sentences, no fluff, with the core action first. Each sentence adds value: what it does, when to use, and how it relates to siblings.

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 single-parameter tool with no output schema, the description fully covers purpose, usage, scoping, and sibling relationships. No obvious gaps remain.

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 covers the single key parameter fully with the omit-to-list behavior. The description adds contextual examples of keys (ticker, address, research notes), enriching the semantics 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?

The description clearly states the tool retrieves a value previously saved via remember or lists all saved keys. It distinguishes itself from siblings by explicitly naming remember and forget, making the resource and action unambiguous.

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?

It explicitly says when to use: 'Use to look up context the agent stored earlier' and mentions alternatives (remember to save, forget to delete). This provides clear guidance on appropriate usage and differentiates from related tools.

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