Skip to main content
Glama

SN Data by Shikshan Nivesh

A dataset across every company

get_dataset
Read-onlyIdempotent

The newest rows of one dataset across all covered companies, for questions like 'which insiders bought this week' or 'latest 8-K results filings'. Filter by date, kind or ticker; page with cursor.

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": {
      "dataset": "<dataset>"
    },
    "name": "get_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly rows on or before this date (year-month-day).
fromNoOnly rows on or after this date (year-month-day).
kindNoOnly rows of this kind, like Purchase for insider trades, Results for events, or New position, Added, Trimmed or Sold out for fund holdings.
limitNoMost rows to return, newest first. Default 50.
cursorNoThe next value from the previous answer.
tickerNoThe company's ticker, like AAPL. BRK.B and BRK-B both work.
datasetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real context beyond them: rows come back newest-first, the scope is all covered companies rather than one, and results are paginated via cursor. It does not mention rate limits or what a cursor expiry does, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no waste: scope and ordering first, then example questions, then the filtering and paging axes. Nothing repeats the schema verbatim and every clause carries information.

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

Completeness3/5

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

For a 7-parameter tool with no output schema, the description covers scope, ordering, filtering, and paging adequately. The significant gap is the required 'dataset' enum of eight opaque values (large-holders, events, short-interest, fund-holdings-13f, etc.), which the description never disambiguates or maps to question types, and it does not clarify overlap with the per-dataset sibling tools.

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 coverage is 86%, so the schema already documents date bounds, kind values, limit default, cursor, and ticker normalization (BRK.B/BRK-B). The description only restates the filter axes ('date, kind or ticker') and pagination without adding format or selection detail, which is the baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ('the newest rows of one dataset') and adds discriminating scope with 'across all covered companies', which separates it from per-company siblings like get_company. It stops short of naming any sibling explicitly, so an agent must infer the cross-company vs per-company split.

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?

Usage is conveyed only through example questions ('which insiders bought this week', 'latest 8-K results filings'), which imply the intended question shapes but never state when to prefer this over get_insider_trades, get_events, or get_financials. There are no exclusions or prerequisites, leaving the choice between this and the per-dataset siblings to inference.

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