Skip to main content
Glama

Htmltext

by io.github.pipeworx-io

Recent Changes

recent_changes
Read-onlyIdempotent

"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since since), GDELT→GNews fallback (news mentions in window — GDELT preferred, GNews when rate-limited or 5xx), USPTO (patents granted; PatentsView API sunset May 2025 so this soft-fails until reactivated). since accepts ISO date ("2026-04-01") or relative shorthand ("7d", "30d", "3m", "1y"). Returns structured changes[] grouped by source + total_changes count + pipeworx:// citation URIs. Use entity_profile instead when you want the static profile (filings + fundamentals + LEI + patents) regardless of window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesEntity type. Only "company" supported today.
sinceYesWindow start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y"). Use "30d" or "1m" for typical monitoring.
valueYesTicker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), description details parallel fan-out to multiple sources, fallback logic, soft-fail for patents, and return structure (changes[], total_changes, citation URIs).

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?

Single paragraph with efficient front-loading of purpose via examples, followed by concise explanation of behavior and parameters. Every sentence adds unique value.

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?

Despite no output schema, the description fully covers tool behavior, parameter usage, return fields, and when to avoid this tool. Agent has all necessary information to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: explains date formats (ISO and relative), recommends '30d' for monitoring, clarifies value can be ticker or CIK, and notes type is limited to company.

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 provides a change feed for a company, covering SEC filings, GDELT/GNews news, and USPTO patents. It gives explicit query examples and distinguishes from sibling tool entity_profile.

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?

Explicitly tells when to use entity_profile instead, explains fallback behavior (GDELT preferred, GNews on rate-limit), and provides guidance on using '30d' or '1m' for typical monitoring.

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

All Htmltext 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.8/5.0
Disambiguation2/5

Several tools have overlapping or nested roles: ask_pipeworx_beta is explicitly identical to ask_pipeworx currently, ask_pipeworx_grounded uses the same router, and polymarket_arbitrage/polymarket_edges both surface mispricings. ai_visibility_check and scan_competitor_ai_presence are also tightly coupled, making tool selection error-prone.

Naming Consistency3/5

Names are uniformly snake_case and mostly readable, but the pattern is mixed: verb-first names like extract_links and discover_tools coexist with noun-first product names like polymarket_edges and entity_profile, plus bare verbs like remember and forget. This breaks the predictable verb_noun convention.

Tool Count2/5

34 tools is far too many for a server named Htmltext, and most tools are unrelated to HTML processing. Even as a broad data-research server, the count exceeds the usual 3-15 sweet spot and includes meta-tools, near-duplicate query modes, and niche utilities that bloat the surface.

Completeness3/5

The set is unusually broad—covering data research, prediction markets, memory, subscriptions, HTML extraction, AI visibility, and package scanning—but no single domain is fully fleshed out. HTML tools only do extraction, prediction-market tools lack a simple market browser, and there is no general web fetch tool. Most gaps can be worked around via ask_pipeworx, but the surface feels like a grab bag rather than a cohesive lifecycle.

Resources