Skip to main content
Glama

SN Data by Shikshan Nivesh

8-K events

get_events
Read-onlyIdempotent

Every 8-K the company filed, newest first: the items, what they report in plain words (results, leadership change, agreements and more), the SEC acceptance time and the filing's address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
kindNoOnly events of this kind, like Results or Leadership change.
limitNoMost rows to return, newest first. Default 25.
tickerYesThe company's ticker, like AAPL. BRK.B and BRK-B both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world read, so safety is covered. The description adds value beyond that by disclosing ordering ('newest first') and the exact shape of each row, which matters because there is no output schema. It does not mention the 25-row default cap or truncation behavior, which keeps it short of a 5.

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?

A single front-loaded sentence that leads with the resource and ordering, then lists row contents. It is dense but readable; the parenthetical 'results, leadership change, agreements and more' is slightly loose but earns its place by showing example kinds.

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 correctly takes on the burden of explaining return contents and ordering, which is exactly what an agent needs to decide whether to call it. The remaining gap is that it omits any mention of filtering and default result size, which are non-trivial for a tool that can return up to 500 rows.

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 ticker format, date patterns, kind, and the limit cap. The description contributes nothing about parameters and does not even hint that date or kind filtering exists. Baseline 3 is appropriate when the schema carries all parameter meaning.

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 names a specific resource (8-K filings) and enumerates what each row contains: items, plain-language summaries, SEC acceptance time, and filing address. It is clear what the tool returns, though it never contrasts itself with siblings like get_company or get_insider_trades, so an agent must infer the boundary from the resource name alone.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. Worse, the framing 'Every 8-K the company filed' implies an unfiltered firehose even though the schema exposes from/to/kind/limit filters, leaving the agent to discover filtering only by opening the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources