Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

SEC red-flag alerts across the market

sec_market_alerts
Read-only

Answers "Did anything bad just get filed?", "Alert me to restatements, auditor changes or CEO departures" or "Which insiders bought stock today?". Alerts from new SEC filings across all public companies, most serious first: RED (8-K item 4.02 restatements, 3.01 delisting notices, 1.03 bankruptcies, NT 10-K late annual reports), AMBER (4.01 auditor changes, 1.05 cybersecurity incidents, 2.06 impairments, 2.04 debt triggers, 5.01 changes in control, NT 10-Q), GREEN (open-market insider purchases of $100K or more, from Form 4s) and INFO (5.02 leadership changes, 2.02 earnings releases, 1.01 agreements, 2.01 deals, 2.05 restructurings, 3.02 unregistered share sales). Each alert has the company, ticker, EDGAR acceptance time, items, a text excerpt for red and amber 8-Ks, the filing link and the paid call that reads it in full. Filter by levels, types or a tickers watchlist. Built for polling: pass the previous answer's cursor as since to get only new alerts, and check the free sec_alerts_peek first so you pay only when there is something new. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.005 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

NameRequiredDescriptionDefault
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
limitNoHow many alerts to return, most serious first, then newest (1-50, default 20).
sinceNoOnly alerts found after this time: pass the previous answer's `cursor` to get just what is new. Default: every alert in the store (about the last day).
typesNoOnly these alert types: bankruptcy, restatement, delisting_notice, late_annual_report, auditor_change, cybersecurity_incident, impairment, debt_acceleration, change_in_control, late_quarterly_report, insider_purchase, leadership_change, earnings, material_agreement, acquisition_or_disposal, restructuring, unregistered_share_sale. Default: all.
levelsNoOnly these levels: red (restatement, delisting, bankruptcy, late 10-K), amber, green (insider buying), info (earnings, leadership changes, deals). Default: all.
tickersNoA watchlist: only alerts for these tickers. Default: the whole market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
+  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
+  "maxLength": 64,
+  "type": "string"
+}
  2. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds genuinely useful non-annotation behavior: pricing ($0.005 USDC via x402), the billing policy (only settled when a result returns; 400/4xx/5xx not charged), store retention (~last day), and ordering (most serious first, then newest). That said, the standard for credit is lower when annotations carry safety, and return format is largely enumerated rather than deeply explained, so a 3 is fitting.

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

Conciseness4/5

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

Front-loaded with representative user questions, then the alert taxonomy, then filters, then the polling/pricing mechanics. It is dense but every sentence carries information; the nested severity enumeration is long but is the tool's core value proposition.

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 exists, and the description compensates by listing the return fields (company, ticker, EDGAR acceptance time, items, text excerpt, filing link, paid read call) plus the cursor-based paging contract and cost model. An agent has everything needed to call and interpret it.

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 the baseline is 3. The description still adds value beyond the schema by mapping `levels` to their constituent item codes, explaining that `since` takes the prior `cursor`, and clarifying that `tickers` acts as a watchlist over the whole market by default.

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?

States a concrete verb and resource (surfacing red-flag alerts from new SEC filings across the whole market) and specifies the scope, severity taxonomy, and the exact filing events covered. An agent can distinguish it from sec_recent_events or sec_insider_trades without opening any schema.

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?

Gives an explicit polling workflow (pass the previous answer's `cursor` as `since`, check the free sec_alerts_peek before paying) and states the cost-gating condition. When-to-use and the cheap alternative are both spelled out rather than implied.

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

All Agent Utility Suite (x402) toolsInspect
Try in Browser
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources