Skip to main content
Glama

edgrapi-skills

by io.github.paperandbeyond23-gif
OverviewDiscussionsAdmin

Get 8-K material events

get_events
Read-onlyIdempotent

8-K material events for a ticker as typed items (2.02 earnings, 5.02 executive change, 1.05 cybersecurity incident, 2.01 acquisition, etc.), each with a notable flag for the market-moving ones and a link to the filing. Pass item to filter to one event type (e.g. '4.02' for every restatement a company filed). Pass ticker='restatements' or 'auditor-changes' for the market-wide red-flag feed of recent item 4.02 / 4.01 8-Ks across all filers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoFor the market-wide feeds: lookback window in days (default 45).
itemNoFilter to a specific 8-K item code, or comma-separated codes, e.g. '4.02' (restatement) or '5.02,2.02'.
limitNoNumber of events, 1-100 (default 20; 50 for feeds).
tickerYesUS stock ticker (e.g. 'AAPL'), or 'restatements' / 'auditor-changes' for the market-wide item feed.
notableNoOnly market-moving events (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "For the market-wide feeds: lookback window in days (default 45).",
+  "type": "integer"
+}
    • addedInput schema / properties / item
      Added value: +{
+  "description": "Filter to a specific 8-K item code, or comma-separated codes, e.g. '4.02' (restatement) or '5.02,2.02'.",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Number of events, 1-100 (default 20)."New value: +"Number of events, 1-100 (default 20; 50 for feeds)."
    • changedInput schema / properties / ticker / description
      Previous value: -"US stock ticker, e.g. 'AAPL'."New value: +"US stock ticker (e.g. 'AAPL'), or 'restatements' / 'auditor-changes' for the market-wide item feed."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already supply readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds behavioral context by explaining that results are typed items, include a notable flag for market-moving events, link to the filing, and that special ticker values change the tool into a market-wide red-flag feed.

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?

Three sentences that front-load the core purpose, then provide filter and special-mode instructions without redundancy. Every sentence adds functional value, and the description is neither bloated nor under-specified.

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?

For a read-only, filtered-list tool with multiple modes, the description covers the essential behaviors: event types, notable filtering, filing links, item filtering, and market-wide feeds. The schema handles parameter defaults and constraints, and the annotations cover safety, so nothing critical is missing for an agent to invoke the tool correctly.

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 all five parameters with meaningful descriptions. The tool description reinforces examples like '4.02' and the special ticker values, but most of that information is duplicated from the schema rather than adding substantial new meaning beyond the structured definitions.

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?

The description opens with a specific verb and resource: 8-K material events for a ticker, presented as typed items with notable flags and filing links. It also clearly distinguishes the market-wide feed modes ('restatements', 'auditor-changes') from the per-ticker use case, so an agent can tell this apart from filing-level sibling tools like get_filings or search_filings.

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?

The description gives concrete usage instructions: pass an item code to filter to a single event type, pass special ticker values for market-wide feeds, and use notable to isolate market-moving events. It does not explicitly name sibling alternatives or state when not to use this tool, but the context is clear enough to guide selection.

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

All edgrapi-skills 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.

Resources