Skip to main content
Glama

Security Feeds

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

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

Discloses that the feed is persisted, that mark_read flags events as read for future calls, and describes the return payload. Annotations already indicate readOnly, idempotent, and non-destructive behavior, so the description adds useful context beyond that.

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?

Four sentences, each purposeful. Front-loaded with main purpose, then details. 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?

Given 5 optional params, no output schema, and annotations covering safety, the description fully explains input options, return format, side effects, and even an alternative access method. An AI agent can confidently use this 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 covers all 5 parameters. Description adds value by giving examples (e.g., 'sec_8k' for type, ISO timestamp for since) and explaining the side effect of mark_read. This goes 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?

Clearly states the tool pulls fired events from the subscription feed and returns the most recent alerts. Differentiates from siblings like fetch_feed or read_feed by specifying scope (recent alerts, subscription feed) and filtering options.

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?

Explicitly says polling works fine and provides an alternative endpoint for scripts/dashboards. Implicitly guides use via filtering parameters but does not explicitly state when to avoid this tool.

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

All Security Feeds 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
Disambiguation2/5

The ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio creates real selection ambiguity — beta is currently identical to the stable router, and grounded shares the same routing with an added evidence step. Polymarket tools also overlap (polymarket_edges vs polymarket_arbitrage both surface structural arbitrage), and entity_profile/recent_changes both pull filings and news.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern (resolve_entity, list_feeds, validate_claim, compare_entities). Minor deviations exist — bare verbs (remember, recall, forget, subscribe, unsubscribe) and noun-first names (entity_profile, recent_changes, pipeworx_trending) — but the overall convention is consistent and readable.

Tool Count2/5

34 tools is excessive for a server nominally named 'Security Feeds' — only three tools actually relate to security feeds. Even as a broad data-research platform, the surface feels bloated with five near-exclusive Polymarket tools, three memory tools, and four subscription-lifecycle tools that could be consolidated.

Completeness4/5

For the actual domain revealed by the tools (data research, entity intelligence, prediction markets, subscriptions, feeds), coverage is strong: resolution, profiles, changes, comparison, claim verification, memory CRUD, subscription lifecycle, and feed operations are all present. Minor gaps include no subscription-update tool and no direct feed-search tool, but the ask_pipeworx router compensates.

Resources