Skip to main content
Glama

zippopotam

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.7/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses key behavioral details: each alert carries source, citation_uri, and raw payload; mark_read:true flips read state so subsequent calls return only newer events. It also openly notes the same feed is accessible at a public URL. No contradiction with 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 sentences, front-loaded purpose, no fluff. Every sentence earns its place: payload composition, filtering, mark_read behavior, polling suitability, and alternative URL.

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 having no output schema, the description tells the agent what the return items contain, how to filter, how mark_read changes subsequent calls, and mentions polling and an alternate REST endpoint. This is fully sufficient for a read-oriented tool with 5 optional parameters.

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 already covers 100% of parameters, so baseline is 3. The description adds value by giving a concrete type example ('sec_8k'), clarifying since as an ISO timestamp with semantics, and explaining the side-effect of mark_read. This goes beyond the schema descriptions, hence a 4.

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,' a specific verb+resource statement that clearly distinguishes this from siblings like list_subscriptions or recent_changes. It also specifies what each alert carries, 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 solid usage context: explains filtering by type/since, mentions 'Polls work fine' to endorse polling, and offers an alternative HTTP endpoint for scripts/dashboards. However, it does not explicitly contrast with similar sibling tools (e.g., recent_changes) or state when not to use it, so it falls short of full guidance.

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

All zippopotam 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 purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim, and bet_research all route questions to the same underlying engine, and ask_pipeworx_beta is explicitly identical to ask_pipeworx right now. The polymarket_* family also has many closely-related entry points, though descriptions do help differentiate them.

Naming Consistency4/5

Names consistently use snake_case with descriptive verb-first patterns (ask_, lookup_, scan_, validate_, resolve_, subscribe) and a clear polymarket_ family prefix. Minor inconsistency exists between lookup_city/lookup_zipcode and resolve_entity, and between noun-style names like entity_profile vs verb-style names like compare_entities, but the overall style is predictable.

Tool Count2/5

33 tools is heavy for a single server, and multiple could be consolidated: the ask_pipeworx variants and deep_research largely overlap, and the memory/subscription categories could be collapsed. For a data-platform gateway the breadth is arguably justified, but the visible redundancy makes the surface feel bloated rather than well-scoped.

Completeness4/5

The core domains are well covered: question answering has multiple modes, entity lookup has resolution and profiling, prediction markets have research/edge/arb/fill-risk coverage, and the memory (remember/recall/forget) and subscription (subscribe/list/unsubscribe/recent_alerts) lifecycles are complete. Minor gaps exist such as no direct tool to fetch a pipeworx:// record by URI, relying instead on MCP resources.

Resources