Skip to main content
Glama

Mempool Space

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

A4.8/5.0
Behavior5/5

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

Beyond annotations (readOnly, idempotent, non-destructive), the description discloses that mark_read:true flags events read, affecting subsequent calls. This mutation side effect is critical for agent behavior and is not covered by annotations. Also explains the feed persistence and return fields.

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 purpose, then details return fields, filtering, side effects, and alternative access. No unnecessary words, every sentence earns its place.

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 tool has no output schema, the description explains return fields adequately. All parameters are described in schema and supplemented by examples in the description. Annotations are rich, and the description covers usage, side effects, and alternative access, making it comprehensive for an agent.

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?

All 5 parameters have schema descriptions (100% coverage). The description adds value by giving concrete examples (e.g., 'sec_8k' for type) and explaining the mark_read parameter's behavior and implications. This enhances understanding 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 pulls fired events from a subscription feed, with specific verbs and resource identification. It distinguishes from sibling tools (none are alert-specific), 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 context for usage by explaining filtering options (type, since) and the mark_read side effect. It also mentions an alternative access method (GET endpoint for scripts/dashboards). However, it does not explicitly compare with sibling tools or state when not to use.

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

All Mempool Space 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

B3.1/5.0
Disambiguation2/5

The set mixes two unrelated domains — Bitcoin mempool explorer tools and the much larger Pipeworx data-query platform — and within the Pipeworx half several tools route to the same 5,743-tool catalog (ask_pipeworx, deep_research, discover_tools, suggest_questions). ask_pipeworx_beta is currently an exact behavioral duplicate of ask_pipeworx, and the polymarket_* family has fuzzy boundaries (arbitrage vs edges vs fill_risk, with fill-checking living in both polymarket_arbitrage and polymarket_fill_risk), so an agent must read long descriptions to avoid misselection.

Naming Consistency3/5

All names use snake_case and there are recognizable sub-families (get_* Bitcoin lookups, ask_pipeworx_*, polymarket_*), but conventions are mixed across the whole set: bare-noun state tools (block_height, hashrate, mempool_stats, mining_pools) sit beside verb_noun actions (get_block, list_subscriptions), and prefix placement is inconsistent (ask_pipeworx vs pipeworx_trending/pipeworx_feedback). The naming is readable but not predictable enough to guess a tool's name from its function.

Tool Count2/5

41 tools is well past the 25+ threshold for a coherent server, and the count is inflated by bundling two unrelated products under a server named after only the smaller half (~10 Bitcoin tools vs ~31 Pipeworx tools). Many Pipeworx tools are convenience wrappers around one universal router, adding surface area without adding genuinely new capabilities.

Completeness3/5

Each half is internally workable: the Bitcoin side covers blocks, transactions, addresses, fees, hashrate, and pools, while the Pipeworx side provides broad query, research, subscription, and memory lifecycles. However, there are notable gaps relative to each domain (no block-list/fee-history endpoints on the explorer side; no direct per-source CRUD on the data side), and no single coherent domain is fully served because the server's stated identity matches only a fraction of its tools.

Resources