Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

How many new SEC alerts (free)

sec_alerts_peek
Read-only

Free, no payment needed. Counts the alerts sec_market_alerts would return for the same since, levels, types and tickers, by level and type, with a new cursor. Counts only: the companies, filings and excerpts come with the paid sec_market_alerts, whose ready-to-send call is included when there is something new. Built for polling: peek for free every few minutes, pay only when new_alerts > 0. Rate-limited per client.

Input Schema

NameRequiredDescriptionDefault
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
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.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds context they cannot: the free/no-payment model, per-client rate limiting, the fact that it returns no company/filing/excerpt content, and that a ready-to-send paid call is bundled when something is new. That is unusually rich behavioral disclosure.

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?

Front-loads the free/counts-only distinction, then the polling rationale. Every sentence carries a distinct fact (cost, scope, output limits, cursor chaining, rate limit) with no padding.

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?

There is no output schema, so the description carries the burden of describing the return shape – counts by level and type plus a new cursor – and it does so. Combined with annotations and full schema coverage, an agent has everything needed to call it correctly and interpret the result.

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, but the description adds meaning beyond the schema by tying the filters to sec_market_alerts' identical semantics and explaining that the returned cursor is the value to pass back into `since` for incremental polling. It does not restate per-parameter syntax, which the schema already handles.

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 'counts the alerts sec_market_alerts would return' – and immediately scopes the result to counts by level and type with a cursor. The sibling relationship to sec_market_alerts is explicit, so an agent can distinguish the two without opening either 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 unambiguous when-to-use: poll for free every few minutes and only call the paid sec_market_alerts when new_alerts > 0. It names the alternative and the exact condition that selects it, leaving nothing to inference.

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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources