Skip to main content
Glama

ExchangeRebel — pay-per-call APIs for AI agents (x402 on Solana)

sec_alerts_poll_alerts

Poll the alerts view of a registered watch: the filings matching the watch's own rules that this service first saw since the cursor — new filings, /A amendments grouped to their base form, and deletion flags from weekly index reconciliation only. Paid via x402: $0.01 — RULED (10000 USDC units / 68000 SOL lamports) per delivered view — one poll delivers ALL matching events since the cursor, up to 200 per poll; it is NOT charged per event. Always call the free preflight first (same watch_id + cursor): GET /toll/secalerts/alerts/preflight returns the pending-event count only (no event content) — pending_count 0 is the complete free answer, so you never pay for an empty view. A settled poll that still delivers zero writes exactly one refund intent (net charge zero, cursor unmoved). If you lose a response, re-poll the same cursor within 7 days: the delivery record is re-served verbatim and free (redelivered: true). first_seen_at is ExchangeRebel's own detection timestamp — the moment this service first recorded the filing in its append-only store. The SEC publishes no availability timestamp, so no seller's first-seen time can be anything other than their own observation. For a filer's first-ever touch, the store is seeded from the filer's returned history and first_seen_at is the seed time (records carry seeded:true). Deletion flags are issued only for removals confirmed by the weekly full-index reconciliation: a deletion_flag event is produced only from a record whose provenance marks it weekly-index-reconciliation-sourced. Removals noticed when a single filer's submissions record is re-read are never issued as deletion alerts by this service. Until the weekly reconciliation is wired to the live store, deletion flags do not fire in production. Honest crossover: polls cost $0.01 (ruled price) per delivered alerts view. A caller whose watches deliver about 500 events a month is spending about $5.00 a month here — the price of Datamule's $5/month subscription — and continuous, high-volume watchers are better served by that subscription. This service is built for episodic, task-driven agent queries: register a watch, poll it when the task needs the answer, and pay only for delivered views. Price: $0.01 per call (per delivered alerts view). — USDC on Solana via x402 (over MCP: call without payment to get the PaymentRequired challenge, then retry with the payment at _meta["x402/payment"]). HTTP equivalent: GET https://exchangerebel.com/toll/secalerts/alerts.

Input Schema

NameRequiredDescriptionDefault
cursorNoOptional opaque cursor from a prior poll's next_cursor (or the registration initial_cursor); omit for the watch's initial cursor. A cursor bound to a different watch is refused free (bad_cursor).
watch_idYesThe bearer credential issued by sec_alerts_register_watch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Far beyond what the annotations convey: pricing model ($0.01 per delivered view, not per event, up to 200 events), x402 payment flow via _meta["x402/payment"], refund-intent behavior on zero-event settled polls, free verbatim redelivery of a lost response within 7 days, and disclosure that deletion flags do not currently fire in production. readOnlyHint=false is consistent with a tool that settles payments and writes delivery/refund records.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose, price, and preflight are correctly front-loaded, but the prose runs long for a two-parameter tool. Several passages — the aside that "no seller's first-seen time can be anything other than their own observation," the seeded-history detail, and the repeated price restatements — could be trimmed without losing call-critical information.

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?

For a paid, stateful, cursor-driven tool with no output schema, everything an agent needs is present: cost, payment mechanics, preflight requirement, refund path, redelivery path, event-type definitions, and the current limitation on deletion flags. Nothing material is left for the agent to infer.

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, but the description adds real semantics: it explains that the cursor delimits "all matching events since the cursor," that a re-poll of the same cursor within 7 days re-serves the delivery verbatim, and that a zero-event poll leaves the cursor unmoved. Those are behavioral facts about the cursor the schema's terse "opaque cursor" note does not convey.

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?

Opens with a specific verb+resource ("Poll the alerts view of a registered watch") and immediately enumerates what counts as an event: new filings, /A amendments grouped to base form, and deletion flags. It clearly distinguishes the tool from its sibling sec_alerts_register_watch and from a plain filing feed by scoping delivery to a watch's own rules and cursor window.

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

Usage Guidelines5/5

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

Explicit routing instructions: "Always call the free preflight first (same watch_id + cursor)" and "pending_count 0 is the complete free answer." It also names the alternative (Datamule's $5/month subscription) and the exact condition that selects it — continuous high-volume watchers — versus this tool's episodic, task-driven use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources