Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

SEC alerts pushed to your webhook (30 days)

sec_alert_subscription

Answers "Tell me the moment any of my holdings files something bad" without polling. One payment covers 30 days: every new alert matching your filters (a tickers watchlist, levels, types; default red, amber and green: restatements, delisting notices, bankruptcies, late 10-K/10-Q, auditor changes, cybersecurity incidents, impairments, changes in control, insider purchases of $100K+) is POSTed to your HTTPS webhook_url as JSON within about 2 minutes of being found, in the same shape sec_market_alerts returns, signed with HMAC-SHA256 using the signing_secret returned once at signup. Failed deliveries are retried every 2 minutes. The webhook must answer a test ping with 2xx or you are not charged. Extend with renew_subscription_id (+30 days); check deliveries or cancel with the free sec_alert_subscription_status. Subscriptions survive server restarts. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $1.00 USDC per 30 days 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).
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.
levelsNoOnly these levels (red, amber, green, info). Default: red, amber and green.
tickersNoWatchlist: only alerts for these tickers. Default: the whole market.
webhook_urlNoYour HTTPS endpoint. New alerts are POSTed to it as JSON, signed (see `verify`). It must answer a test ping with 2xx, or you are not charged.
renew_subscription_idNoExtend this subscription by 30 days instead of creating one (its webhook and filters stay).

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

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

Well beyond annotations, it discloses HMAC-SHA256 signing with a signing_secret issued once at signup, ~2-minute delivery latency, 2-minute retry cadence, restart survival, the test-ping requirement, and precise billing semantics (charged only on returned result; 400 and 4xx/5xx not settled). Annotations only give the generic readOnly/openWorld/idempotent profile, so this extra operational detail is genuinely additive.

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 the use case and pricing, and nearly every sentence carries distinct operational information. It is a single dense run-on paragraph, however, and re-lists filter values already present in the schema, so it is not maximally tight.

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, yet the description explains the delivered payload shape (same as sec_market_alerts), the transport, signature scheme, retries, error treatment, cost, and lifecycle. An agent has everything needed to invoke it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: the levels default of red/amber/green, the whole-market default for tickers, the extend-by-30-days behavior of renew_subscription_id, and the relationship between signing_secret and webhook_url. It only partially elaborates the type enums it re-lists.

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 specific verb and resource: it creates a paid 30-day subscription that POSTs SEC alerts matching supplied filters to an HTTPS webhook. It distinguishes itself from siblings by naming sec_market_alerts as the shape source and sec_alert_subscription_status as the free status/cancel path.

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?

Opens with the exact user intent it serves ('tell me the moment any of my holdings files something bad, without polling'), then gives when-to-use-this variants: create new vs. extend via renew_subscription_id vs. cancel/check with sec_alert_subscription_status. Alternatives and preconditions (2xx test ping) are explicit.

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