Skip to main content
Glama
Sign In

AgentFeed

by io.github.seekdaseek
OverviewDiscussionsAdmin

SEC 8-K events

get_sec_8k
Read-onlyIdempotent

Use when an agent needs the material events US companies disclosed in the last hours. Returns the 8-K filings filed across the market in the window, with company, CIK, filing time, accession number, the 8-K item codes and titles (e.g. 2.02 results, 5.02 officer changes, 1.01 agreements) and a count per item. Source: SEC EDGAR current filings. Costs 0.01 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_sec_8k"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNolook-back window in hours, 1-72, default 24

Output Schema

NameRequiredDescriptionDefault
dataYesthe get_sec_8k payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_sec_8k
toolYesthe tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / hours / maximum
      Added value: +72
    • addedInput schema / properties / hours / minimum
      Added value: +1
    • changedInput schema / properties / hours / type
      Previous value: -"number"New value: +"integer"
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), but the description adds material context they don't: the upstream source (SEC EDGAR current filings) and that each call costs 0.01 USDC via x402 across five chains. The per-call charge is the kind of cost behavior an agent must know before invoking. It doesn't mention failure/empty-window behavior or latency.

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 usage trigger, then the return shape, source, and cost in four tight sentences with no filler. The item-code enumeration is useful but slightly verbose given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, an output schema, and a fully documented single parameter, the description covers what remains: source, cost, and the fields returned. The one meaningful omission is how this differs from get_sec_filings, which matters given the crowded sibling set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single 'hours' parameter is fully documented in the schema (range 1-72, default 24), so the schema carries the semantics. The description only alludes to it via 'in the last hours' and 'the window' without adding format or default details. Baseline 3 is appropriate at 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource+scope: 8-K filings filed market-wide in a look-back window, with named return fields (CIK, accession number, item codes). It is clear what the tool returns, but it never distinguishes itself from the sibling get_sec_filings, which an agent will see in the same list.

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

Usage Guidelines4/5

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

'Use when an agent needs the material events US companies disclosed in the last hours' gives a clear triggering condition tied to recency and materiality. It stops short of naming an alternative or exclusion (e.g. get_sec_filings for historical or company-specific lookups), leaving the sibling choice to inference.

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

All AgentFeed toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources