Skip to main content
Glama

Rba

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

A3.8/5.0
Behavior1/5

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

The description discloses that setting mark_read:true flags events as read and affects future calls, which is a behavioral trait. However, the annotations declare readOnlyHint:true, which contradicts this documented side effect. Since the description contradicts the annotation, the score is 1 per the rubric.

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 four concise sentences, front-loaded with the purpose, and every sentence adds useful information. It includes the key behavior, filtering options, mark_read effect, and an alternative access URL without any fluff.

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 five optional parameters and no output schema, the description explains what the returned events contain (source, citation_uri, raw payload), how filtering works, and the mark_read side effect. It could mention pagination limits or the exact shape of the payload, but it's adequate for most use cases.

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 coverage is 100%, so the baseline is 3. The description adds value by giving a concrete type example ("sec_8k"), explaining the downstream effect of mark_read, and mentioning the citation_uri and raw payload content. This goes beyond the schema's descriptions.

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,' which names a specific action and resource. It clearly distinguishes this tool from siblings like list_subscriptions and recent_changes by focusing on reading fired alerts, not managing subscriptions or tracking changes.

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 states when to use the tool ('Pull fired events...'), how to filter by type and since, and even provides an alternative access method (the same feed at a URL). It doesn't explicitly name alternative tools, but the context is clear and practical.

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

All Rba 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.7/5.0
Disambiguation2/5

Several tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route natural-language questions to the same underlying catalog, and polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, and polymarket_kalshi_spread all target prediction-market opportunities. entity_profile, recent_changes, and compare_entities also share company-research territory, making misselection likely without reading long descriptions carefully.

Naming Consistency3/5

All names use snake_case, but conventions are mixed: some are verb_noun (list_subscriptions, generate_llms_txt, resolve_entity), some are noun phrases (entity_profile, rba_cash_rate), and some are brand-prefixed product names (ask_pipeworx, pipeworx_trending). The polymarket_* and rba_* families are internally consistent, but the overall surface has no single predictable pattern.

Tool Count2/5

35 tools is a large surface, well above the 25+ threshold that typically becomes unwieldy. While the server covers a broad domain (data lookup, prediction markets, memory, subscriptions, company research), many tools are niche variants (ask_pipeworx_beta, polymarket_edge_tracker, scan_competitor_ai_presence) that add cognitive load rather than earning their place.

Completeness3/5

Core flows are well covered: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and data access has ask_pipeworx plus grounded and research variants. However, the surface is sprawly and uneven — prediction markets get six tools while other domain areas rely on generic routing, and the server's overall purpose is diffuse enough that gaps are hard to assess cleanly.

Resources