Skip to main content
Glama

Scb Se

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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate read-only, idempotent, not destructive. The description adds that it returns most recent alerts with specific fields, explains mark_read and unread_only behavior, and mentions polling suitability. No contradictions.

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 conveying essential information without redundancy. Front-loaded with main purpose, then details. Every sentence adds value.

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?

No output schema, so description compensates by listing returned fields (source, citation_uri, raw event payload) and explaining filter/mark_read behavior. Also notes polling and alternative access method. Completes the picture for a read-only list 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% with clear descriptions. The description adds semantic value for type (example) and mark_read (effect on subsequent calls). Limit and unread_only are explained in schema, so additional benefit is moderate.

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 your subscription feed' and specifies the returned data (source, citation_uri, raw payload). This distinguishes it from sibling tools like list_subscriptions which list subscriptions, not events.

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?

Provides guidance on filtering by type and since, and the effect of mark_read. Mentions polling is fine and points to an alternative URL for scripts/dashboards. Does not explicitly state when not to use, but context is clear.

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

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

Most tools have clearly distinct purposes, but several overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (only differing in verification/depth), and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_fill_risk / polymarket_kalshi_spread all target similar prediction-market signals, which could cause mis-selection without careful reading.

Naming Consistency4/5

Most names follow a clear verb_noun pattern (resolve_entity, query_table, remember, recall, forget, subscribe, unsubscribe, validate_claim, compare_entities, search_within), but there are exceptions like ai_visibility_check (adjective_noun), generate_llms_txt (verb_noun with dot), and several polymarket_* names that are fine but inconsistent with the snake_case verb-first convention.

Tool Count5/5

35 tools is a large but reasonable surface for a broad data/serach platform covering company financials, economics, prediction markets, memory, subscriptions, and discovery. The count is justified by the wide domain, and the set is not bloated with trivial duplicates.

Completeness4/5

The surface covers core CRUD for entities (resolve, profile, compare, search, query) and memory (remember/recall/forget), plus subscriptions and meta-tools. Minor gaps: no explicit tool for updating/creating entities (understandable for a read-only data service), and no tool for listing all available table schemas beyond discovery (subjects covers this). Overall strong coverage.

Resources