Skip to main content
Glama

Bart

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

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

Descriptions adds details beyond annotations: explains each returned field (source, citation_uri, payload), the effect of mark_read on read status, and that polls work fine. No contradiction with annotations (readOnlyHint=true, etc.).

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 a single paragraph of four sentences, each earning its place: purpose, return structure, filtering, mark_read and polling alternative. No wasted words.

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?

Coverage is excellent: explains return fields, all filtering options, side effect of mark_read, and alternative access. Minor omission of unread_only parameter explanation, but schema covers it. For a tool with 5 parameters and no output schema, this is very complete.

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?

Although schema has 100% description coverage, the description adds valuable context like example values (e.g., 'sec_8k' for type) and clarifies ISO timestamp format for since. It also explains mark_read effectively.

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 starts with 'Pull fired events from your subscription feed', clearly stating the verb (pull) and resource (fired events). This distinguishes it from sibling tools like list_subscriptions or subscribe.

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 clear context: filtering by type and since, and the mark_read behavior. It also mentions polling works fine and gives an alternative API endpoint for scripts/dashboards. However, it does not explicitly contrast with siblings or state when not to use it.

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

All Bart 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

A4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the three ask_pipeworx variants (stable, beta, grounded) overlap significantly in functionality, as do the Polymarket tools (bet_research, arbitrage, edges, etc.), which could cause an agent to misselect without careful reading of descriptions.

Naming Consistency3/5

Naming follows multiple styles: verb_noun (ask_pipeworx, compare_entities), domain first (polymarket_arbitrage, bart_departures), and single words (remember, forget). There is no consistent pattern, making the set feel disjointed.

Tool Count3/5

35 tools is on the heavy side for a single server. While each tool has a defined role, the count suggests potential for consolidation (e.g., merging ask_pipeworx variants or Polymarket tools). The server's broad scope partially justifies the count.

Completeness4/5

The tool surface covers a wide range of functionalities: structured querying, entity lookup, comparison, fact-checking, subscription management, memory, and domain-specific tools for BART and Polymarket. Minor gaps exist (e.g., no direct API for some data sources), but overall it feels comprehensive.

Resources