Skip to main content
Glama

insidergraph

by com.insidergraph

Search material corporate events

get_material_events
Read-onlyIdempotent

Search SEC 8-K material corporate events (bankruptcies, restatements, officer departures, delistings, cyber incidents, earnings, M&A...) normalized to item codes, with SEC filing links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows per page, default 50, cap 500.
sinceNoEarliest event date, YYYY-MM-DD.
untilNoLatest event date, YYYY-MM-DD.
cursorNoOpaque pagination token from the previous response's page.next_cursor; pass it back verbatim to fetch the next page.
tickersNoTicker symbols to include, e.g. ["NVDA"]. Empty = all issuers.
item_codesNo8-K item numbers, e.g. ["1.03","5.02"]. 1.03=bankruptcy, 4.02=restatement, 5.02=officer departure, 1.05=cyber incident, 2.02=earnings, 8.01=other.
high_signalNoOnly distress-grade items (1.03, 1.05, 2.04, 2.06, 3.01, 4.02, 5.02). Overrides item_codes.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / item_codes / items / enum
      Added value: +[
+  "1.01",
+  "1.02",
+  "1.03",
+  "1.04",
+  "1.05",
+  "2.01",
+  "2.02",
+  "2.03",
+  "2.04",
+  "2.05",
+  "2.06",
+  "3.01",
+  "3.02",
+  "3.03",
+  "4.01",
+  "4.02",
+  "5.01",
+  "5.02",
+  "5.03",
+  "5.04",
+  "5.05",
+  "5.06",
+  "5.07",
+  "5.08",
+  "6.01",
+  "6.02",
+  "6.03",
+  "6.04",
+  "6.05",
+  "7.01",
+  "8.01",
+  "9.01"
+]
  2. Changed3 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / default
      Added value: +50
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds useful behavioral context about normalization to item codes and SEC filing links, but it does not disclose result shape, coverage limits, or pagination behavior beyond what the cursor schema implies.

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?

One dense sentence that front-loads the core purpose, lists representative event types, and notes the two key output characteristics (normalization and SEC links). There is no wasted text.

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?

Given the detailed input schema, read-only annotations, and mention of SEC filing links, the description is largely sufficient for invoking the tool correctly. The main gap is the lack of an explicit return-structure description, though the cursor parameter's schema hints at a page.next_cursor response field.

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 input schema already documents all seven parameters and their meanings. The description's mention of item codes aligns with the item_codes parameter but adds little beyond the schema's existing enum explanations.

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 uses a specific verb and resource ('Search SEC 8-K material corporate events') and enriches it with concrete examples (bankruptcies, restatements, officer departures, cyber incidents). It does not explicitly contrast against siblings like list_recent_filings or get_insider_trades, but the scope is specific enough that an agent can infer the domain.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus alternatives, nor are exclusions or preferred conditions stated. The sibling tools cover related data like insider trades and filings, so an explicit routing hint would materially help; without it, the agent must rely on inference.

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

All insidergraph toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

Each tool has a clearly distinct job: per-feed searches, cross-feed signals, entity resolution, coverage orientation, profile aggregation, and a recent-filings firehose. Even overlapping areas like Form 144 are cleanly separated between raw search (get_planned_sales) and matched analytics (planned_vs_executed). An agent should rarely pick the wrong tool.

Naming Consistency3/5

Most tools follow a readable verb_noun pattern such as get_insider_trades, find_company, and list_recent_filings. However, company_profile is a noun-only name, and planned_vs_executed plus trades_before_events are descriptive labels rather than commands, making the overall convention mixed though still understandable.

Tool Count5/5

11 tools is well-scoped for an SEC insider-data server: four feed-specific searches, three cross-feed signals, a company resolver, a profile aggregator, a coverage guide, and a firehose. Each tool earns its place and none feels redundant.

Completeness5/5

The set covers all core SEC feeds (Forms 3/4/5, 8-K, 144, 13D/13G) plus identifier resolution, recent filings, an aggregated company profile, and sophisticated cross-feed analytics. For a read-only data service, there are no obvious dead ends or missing operations that would strand an agent.

Resources