Skip to main content
Glama

Agent Utility Suite (x402)

by io.github.vanakenj45
OverviewDiscussionsAdmin

Today's earnings releases (SEC 8-K 2.02)

sec_earnings_today
Read-only

Answers "Who reported earnings this morning?", "How did the banks do today?" or "Did any of my holdings report?". Lists the earnings releases (8-K item 2.02, Results of Operations and Financial Condition) filed with the SEC on a day across all companies, newest first. For each: company, ticker, EDGAR acceptance time, the press release's headline, its highlights (subheadlines and the sentences carrying revenue, EPS, net income, margins and guidance figures), the opening paragraph, and links to the press release (EX-99.1) and the filing. Filter with a tickers watchlist; poll with since = the previous answer's cursor to get only new releases (the free sec_alerts_peek with types ["earnings"] counts them first). A day without releases (or none from the watchlist) is a free 404. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.01 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).
dateNoThe filing day (YYYY-MM-DD, US Eastern), or "latest" for the most recent day with releases (e.g. on a weekend). Default: today. EDGAR's live feed reaches back a few business days.
limitNoHow many releases to read, newest first (1-30, default 10).
sinceNoOnly releases EDGAR accepted after this time: pass the previous answer's `cursor` to get just the new ones.
tickersNoA watchlist: only releases from these tickers. Default: every company.

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?

Annotations cover safety (readOnly, non-destructive, openWorld, non-idempotent), but the description adds substantial economic and behavioral context beyond them: a free 404 when no releases exist, billing only on returned results, non-settlement on 400/4xx/5xx, and the $0.01 USDC x402 cost. It also describes the full return payload shape, which matters since there is no output schema.

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?

Dense and front-loaded — the purpose, use cases, and return fields come first, with billing details last. It is longer than strictly necessary and some billing sentences could be tightened, but almost every clause carries operational 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?

With no output schema, the description fully enumerates what each result contains (company, ticker, EDGAR acceptance time, headline, revenue/EPS/margin/guidance highlights, opening paragraph, EX-99.1 and filing links), so an agent can consume the response without guessing. Nothing needed to call or interpret it is missing.

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 real semantics: the cursor-chaining pattern ('pass the previous answer's cursor' into `since`) and the watchlist framing for `tickers`. It also explains the default day and the weekend/`latest` intent, though the schema largely carries the field documentation.

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 (lists SEC 8-K item 2.02 earnings releases) with clear scope (a day, across all companies, newest first) and immediately distinguishes itself from siblings like sec_list_filings and sec_recent_events. The opening example questions anchor the intent precisely.

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?

Names concrete use cases ('Who reported earnings this morning?'), the watchlist filter, the cursor-polling pattern, and an explicit cheaper alternative (free sec_alerts_peek with types ["earnings"] counts them first). When-to-use and when-to-use-something-else are both covered.

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