Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Bulk, Block & Insider Deals

get_stock_deals
Read-onlyIdempotent

Get large-trade history for a stock — bulk deals, block deals, insider (designated-person) trades, and SAST (substantial acquisition) disclosures, with the counterparty name, buy/sell side, quantity, price, and value, newest first. Insider/SAST rows are filings (record: filing, with disclosure date, category, holdings) or older summary rows for months without filings (record: summary; see meta.coverage_note). Answers 'who has been buying or selling X?'. Optionally filter by deal type. price is as traded; price_adjusted is the same price on the split/bonus-adjusted basis of the daily closes, so compare a pre-split/bonus deal with the close using price_adjusted. While meta.has_more, pass meta.next_cursor as cursor.

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter to a single deal type. Omit for all types.
limitNoMax deals (default 25, max 100)
cursorNometa.next_cursor of the previous page (same symbol and type).
symbolNoREQUIRED. Stock symbol, e.g. "RELIANCE" or "TCS".
tickerNoAlias for `symbol`.
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "meta.next_cursor of the previous page (same symbol and type).",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add real substance — and it does: newest-first ordering, the `record` distinction between filing and summary rows with a pointer to meta.coverage_note, and the split/bonus adjustment caveat for comparing `price_adjusted` to closes. Missing only a note on rate limits or result-size limits beyond the 100 cap.

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?

Front-loaded with the resource and the record types, then the analytical use case, then field semantics, then pagination. Dense but nearly every clause carries information; the stacked parentheticals around the insider/SAST record distinction are the one place readability suffers.

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?

With no output schema, the description carries the return-shape burden and does so: it names the per-row fields (counterparty, side, quantity, price, value), the two `record` variants, and the meta fields (`has_more`, `next_cursor`, `coverage_note`). An agent can call and interpret results without further documentation.

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 every parameter including the enum, cursor semantics, and aliases; that sets the baseline at 3. The description adds some meaning — that `type` can be omitted, that `price_adjusted` is the field to compare against closes — but most of its parameter phrasing restates the schema.

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?

States a specific verb+resource ('Get large-trade history for a stock') and enumerates the exact record families it covers (bulk, block, insider/designated-person, SAST), plus the fields returned. It does not explicitly distinguish itself from the likely-overlapping sibling get_stock_ownership, leaving the boundary to be inferred.

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 framing question "Answers 'who has been buying or selling X?'" gives an implied use case, and 'Optionally filter by deal type' clarifies the filter's optionality. There is no explicit when-not guidance or named alternative tool, so the agent must infer the boundary from sibling names.

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.