Skip to main content
Glama

Data Nl

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate read-only, open-world, idempotent, and non-destructive. The description adds behavioral details such as mark_read advancing the read cursor and the structure of returned events (source, citation_uri, payload). No contradictions 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?

The description is three sentences: purpose, return structure, parameters with behavioral notes, and alternative access. Every sentence adds value, no waste.

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 sufficiently explains return format, filtering, read-state management, and polling suitability. All key aspects are covered for this 5-parameter tool.

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?

All parameters are described in the schema (100% coverage). The description adds meaning beyond the schema, e.g., for mark_read it explains that setting it true causes future calls to show only newer events. This extra context justifies a score above baseline 3.

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 'Pull fired events from your subscription feed' with a specific verb and resource. It differentiates from sibling tools like list_subscriptions (which lists subscriptions) by focusing on retrieving alert events.

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 explains filtering options and notes that polling works and an alternative endpoint exists. While not explicitly stating when not to use this tool, it provides sufficient context for appropriate use.

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

All Data Nl 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

Several tool families have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-duplicates (the beta is currently identical), and the six polymarket_* tools plus bet_research heavily overlap in prediction-market analysis. ai_visibility_check and scan_competitor_ai_presence also serve the same core function. An agent would frequently need to read lengthy descriptions to pick the right one, and could easily misselect.

Naming Consistency3/5

Most tools follow a readable snake_case pattern, but the style is mixed: some are verb-first (ask_pipeworx, search_datasets, resolve_entity), some are domain-prefixed nouns (polymarket_edges, pipeworx_feedback), and a few are bare nouns or adjective-noun phrases (dataset, entity_profile, recent_alerts). It is not chaotic, but there is no single predictable verb_noun convention across the set.

Tool Count2/5

With 34 tools, this is above the 25+ threshold considered too many for a coherent toolset. The count is inflated by near-duplicate families (three ask_pipeworx variants, six polymarket tools) that could reasonably be consolidated. While the server covers a broad domain, the number of top-level choices creates unnecessary selection burden for agents.

Completeness4/5

For a read-focused data/research gateway, the surface is quite complete: general lookup, grounded verification, deep research, entity resolution, comparisons, change tracking, memory, subscriptions, and feedback are all present. Minor gaps exist, such as no direct fetch-by-URI tool for the pipeworx:// citations that other tools return, and the Dutch open-data tools are strictly read-only. These are workarounds rather than dead ends.

Resources