Skip to main content
Glama

Gnews

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

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by explaining mark_read behavior ('flag returned events read so the next call only shows newer ones') and that the feed is persisted. This goes beyond the annotations without contradiction.

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 concise, with the key action in the first sentence. It covers purpose, output fields, filtering, mark_read effect, and alternative access in just a few sentences without redundancy.

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?

Despite no output schema, the description lists key return fields (source, citation_uri, raw payload). It explains filtering by type and since, and the mark_read option. However, it omits mention of 'limit' and 'unread_only' parameters, though these are well-described in the schema. Overall, it provides sufficient context for a read-only 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?

Schema description coverage is 100% for 5 parameters. The description reinforces 'type' and 'since' usage with examples like 'sec_8k' and ISO timestamp. It explains the behavioral effect of mark_read on subsequent calls, which adds context not present in the schema description alone.

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 clearly states the verb (pull/returns) and resource (alerts from subscription feed). It explains the output includes source, citation_uri, and payload, setting it apart from sibling tools like list_subscriptions or search_news.

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 guidance that polling works fine and mentions an alternative direct API endpoint for scripts/dashboards. However, it does not explicitly state when not to use this tool or compare it to other sibling tools like ask_pipeworx or search_news.

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

All Gnews 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
Disambiguation4/5

Most tools have distinct, well-described purposes, but there is some overlap, especially among prediction market tools (bet_research, polymarket_arbitrage, etc.) and between ask_pipeworx and ask_pipeworx_grounded. Agents might occasionally select the wrong tool without careful reading.

Naming Consistency3/5

Tool names follow a mix of snake_case and camelCase (e.g., ai_visibility_check vs discover_tools). Some names are descriptive but inconsistent in style (subscribe, unsubscribe, list_subscriptions). Pattern is not uniform.

Tool Count3/5

With 32 tools, the server covers many domains (news, financials, prediction markets, entity resolution, memory). While each tool has a justification, the count feels heavy for a single server, and some tools could be consolidated.

Completeness3/5

The tool set spans a wide range of data sources and operations, but there are notable gaps. For news, only search and top headlines exist without advanced filtering. Prediction markets lack order placement tools. The broad scope means depth is sacrificed in some areas.

Resources