Skip to main content
Glama

Jina Reader

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

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds that each alert carries source, citation_uri, and raw payload, and explains that setting mark_read:true flags events as read so the next call shows only newer ones. This provides specific behavioral context beyond the 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 a single paragraph of five sentences, with the purpose stated upfront. Every sentence provides necessary detail without repetition or fluff. The structure is efficient and front-loaded.

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?

The description covers the core return fields (source, citation_uri, raw payload), filtering options, and the mark_read side effect. It also mentions the external URL as an alternative. While it lacks explicit pagination details beyond the limit parameter, the description is adequate for a read-only tool with annotations covering safety.

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 baseline is 3. The description adds value by giving an example filter ('sec_8k'), specifying the ISO timestamp format for 'since', and explaining the effect of 'mark_read:true'. This enhances understanding beyond the schema 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 opening clause 'Pull fired events from your subscription feed' immediately states the action (pull) and resource (fired events from subscription feed). It further specifies 'returns the most recent alerts' and mentions filtering, making the scope clear. Among sibling tools, none directly duplicate this functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises that 'Polls work fine' and provides an external URL as an alternative for scripts/dashboards, giving some context. However, it does not explicitly state when to use this tool over sibling tools like 'list_subscriptions' or 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 Jina Reader 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
Disambiguation2/5

Multiple tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and specialized tools like entity_profile or validate_claim that can answer similar questions. This creates ambiguity for an agent trying to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern, with most using a verb_noun structure (e.g., ask_pipeworx, compare_entities, resolve_entity). There are no mixed conventions or chaotic naming.

Tool Count3/5

With 31 tools, the server is on the heavy side. While each tool has a distinct purpose, the number is borderline for a coherent set and could be streamlined, especially given the overlapping functionality.

Completeness3/5

The tool set covers a wide range of query and analysis tasks, including data lookup, comparison, betting research, memory, and subscriptions. However, there are notable gaps (e.g., no update/delete for most data, no user management) and some tools seem out of place (e.g., generate_llms_txt).

Resources