Skip to main content
Glama

Newsdata

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

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

Annotations already declare readOnly, idempotent, non-destructive. Description adds valuable behavioral info: the mark_read parameter flags events as read, affecting future calls. This goes beyond annotations and is crucial for correct use.

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?

Five sentences, well-structured, front-loaded with clear purpose. Every sentence adds value; no 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?

Given no output schema, description covers return fields, filtering, mark_read, and alternative endpoint. Lacks pagination details and error handling, but sufficient for a read 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 coverage is 100%, but description adds examples (e.g., 'sec_8k' for type) and explains mark_read's effect, enriching understanding beyond the schema.

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 it pulls fired events from the subscription feed and returns recent alerts with specific fields. It distinguishes from sibling tools like list_subscriptions (which manages subscriptions) by focusing on event retrieval.

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 context: polling works fine, and mentions an alternative endpoint for scripts/dashboards. However, it doesn't explicitly state when not to use this tool or compare it to siblings beyond the alternative.

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

All Newsdata 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
Disambiguation3/5

Most tools have clearly distinct roles, and the extensive descriptions help differentiate intent, but the ask_pipeworx family—especially ask_pipeworx_beta, which is currently identical to ask_pipeworx—creates real ambiguity. Overlapping entry points like ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim could also cause misselection without careful reading.

Naming Consistency4/5

All 34 tools use consistent snake_case, and clear verb-led or noun-prefixed patterns emerge across families like ask_pipeworx*, polymarket_*, and remember/recall/forget. Minor deviations such as ai_visibility_check and recent_changes being noun phrases rather than verb_noun constructions prevent a perfect score.

Tool Count2/5

34 tools is well above the 25-tool threshold for over-scoping, making the set heavy for an agent to navigate. While the server spans many domains, several tools like generate_llms_txt, scan_dependency, and ai_visibility_check feel tangential to the core news/research purpose and would be better split into separate servers.

Completeness4/5

The core news/research domain is well covered: lookup, grounded verification, deep multi-source research, entity profiles, comparisons, subscriptions, and alert feeds are all present with no obvious dead ends. Minor gaps exist—such as no direct full-text article retrieval or a dedicated free-text news search beyond latest_news filters—but agents can work around them.

Resources