Skip to main content
Glama

Hex Pm

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).

Schema Changelog

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

  1. Added

TDQS

A3.8/5.0
Behavior1/5

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

The description states that setting mark_read:true 'flag returned events read' and 'the next call only shows newer ones', which implies a mutating side effect. This directly contradicts the readOnlyHint annotation that declares the operation as read-only. Therefore, the description contradicts the annotation, warranting a score of 1.

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 three sentences, front-loaded with the main purpose, and every sentence provides useful information without redundancy. It efficiently covers output fields, filtering, stateful behavior, and an alternative access method.

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 tool with 5 optional parameters and no output schema, the description sufficiently explains the return payload (source, citation_uri, raw event payload) and key behaviors. It does not mention unread_only and limit, but those are well-covered in the schema. The external endpoint note adds completeness. Minor gap: no mention of pagination or what happens with mark_read when combined with unread_only.

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 covers all parameters with descriptions (100% coverage), so baseline is 3. The description adds value by providing a concrete type example ('sec_8k'), explaining the ISO timestamp for 'since', and clarifying the effect of mark_read on subsequent calls, which adds meaning 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 uses a specific verb 'Pull' and resource 'fired events from your subscription feed', clearly distinguishing it from sibling tools like list_subscriptions or recent_changes. It explains the returned payload and filtering capabilities.

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?

Provides clear context for use: retrieving alerts from the feed, support for polling, and filters. It also offers an alternative endpoint for scripts/dashboards. However, it does not explicitly name when NOT to use this tool or compare it to sibling tools like recent_changes.

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

All Hex Pm 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 occupy overlapping question-answering territory: ask_pipeworx_beta currently behaves identically to ask_pipeworx, while ask_pipeworx_grounded, deep_research, and validate_claim all route the same data catalog and differ mainly in output guarantees. The six Polymarket tools also split edge detection, arbitrage, and fill-risk in ways that are easy for an agent to conflate. Clear exceptions like the memory and subscription trios keep it from a 1.

Naming Consistency4/5

Names are uniformly lowercase snake_case and most follow a readable verb-first or domain-prefixed pattern (get_package, list_releases, scan_dependency, ask_pipeworx_*). The Polymarket family uses noun phrases after a prefix (polymarket_edges, polymarket_fill_risk) and a few names are noun-first (entity_profile, recent_changes), which is a minor inconsistency rather than chaos.

Tool Count2/5

35 tools is well beyond the comfortable 3-15 range and even above the 16-25 heavy range. The broad Pipeworx data scope justifies some expansion, but identical ask_pipeworx_beta, six overlapping Polymarket tools, and unrelated utility families (Hex.pm, AI visibility, memory, llms.txt) suggest bloat rather than deliberate scoping.

Completeness4/5

Within its main data-access purpose, the surface is unusually complete: query (ask_pipeworx), grounded verification (ask_pipeworx_grounded/validate_claim), deep research, entity resolution/profiling, comparison, change feeds, and search-within are all present, and memory/subscription subdomains have full CRUD. There are minor gaps for the package side (no docs/dependents) and the hodgepodge of domains makes a single 'complete' surface hard to define, but no workflow hits a hard dead end.

Resources