NetNest Design Fundamentals API

SEC filing events across companies

get_events

Read-onlyIdempotent

SEC filing events across companies, newest first: 8-K items by plain name, Form 4 insider transactions and Schedule 13D and 13G stakes, each with its form, filing date, acceptance time, accession number, SEC link, CIK and ticker.

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_events"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Number of events, 1 to 100 (default 100)
`since`	No	Cursor from an earlier answer (its next field): only events newer than it are returned
`types`	No	Event types to include, for example 8k_results or form4_transaction
`before`	No	Cursor from an earlier answer (its continue field): the next page of older events
`tickers`	No	Tickers to include, for example AAPL or BRK.B

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful disclosure beyond that: it states the ordering is newest first and enumerates the event categories and returned fields, though it does not explain pagination behavior or rate limits.

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?

The definition is a single front-loaded sentence. Every clause earns its place by stating scope, ordering, event types, and output fields without repetition.

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 no output schema, the description usefully lists the fields each event includes and names the event categories. It remains slightly incomplete because it does not mention pagination or distinguish this tool from get_events_head, but the core information an agent needs is present.

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?

Schema description coverage is 100%, so the schema already documents limit, since, before, types, and tickers. The description adds event-type context by naming 8-K, Form 4, 13D, and 13G categories, but it does not clarify cursor semantics or parameter usage beyond what the schema provides.

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?

The description states a specific resource and scope: SEC filing events across companies, ordered newest first, with concrete event categories and returned fields. It is clear what the tool returns, though it does not explicitly differentiate itself from the similarly named sibling get_events_head.

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

Usage Guidelines3/5

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

The phrase 'newest first' implies a recency-oriented event feed, but there is no explicit guidance on when to use this tool instead of get_events_head or get_history. The usage context is inferable rather than stated.

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

All NetNest Design Fundamentals API tools Inspect

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

Need Help?