Skip to main content
Glama
screener-mcp
by LogeshR15

get_bulk_deals

Read-only

Find NSE bulk deals for a specific stock or investor by symbol or name and look-back period, so you can track large single trades exceeding 0.5% of a company's equity.

Instructions

NSE bulk deals (single trades > 0.5% of a company's equity) — for one company, for one investor across the market, or both.

symbol: restrict to one company ("YESBANK") name: partial investor/entity name ("Jhunjhunwala", "SBI Mutual Fund", "Nalanda") — matched against the deal's client name days: look-back (default 30, max 365; NSE serves one day per request, so only the most recent 90 days are searched)

Pass at least one of symbol / name. Bulk deals miss gradual accumulation — for aggregate FII/DII/promoter holdings use get_shareholding_pattern, for promoter/KMP trades of any size use get_insider_trading.

Examples: get_bulk_deals("ADANIENT", days=60) get_bulk_deals(name="Mutual Fund") get_bulk_deals("TCS", name="SBI Mutual Fund")

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

Input Schema

NameRequiredDescriptionDefault
daysNo
nameNo
symbolNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds a genuine behavioral caveat that the days parameter is silently capped at ~90 days in practice because "NSE serves one day per request." That is exactly the kind of hidden limitation the schema does not reveal. It stops short of noting upstream rate limits or failure behavior under that per-day fan-out.

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?

Front-loaded with the definition, then a per-parameter block, then the constraint and alternatives, then three compact examples. Every line earns its place and the example calls demonstrate the three supported query shapes in minimal space.

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?

An output schema exists, so return values need not be described; within that division of labor the description covers scope, parameter meaning, the real-world look-back cap, and routing to sibling tools. Nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does so: symbol is scoped to one company with a concrete example, name is documented as a partial match against the deal's client name with three sample forms, and days is given a default (30), a max (365), and an effective search horizon (90). No parameter is left ambiguous.

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?

Opens with a specific verb+resource ("NSE bulk deals") and immediately defines the concept ("single trades > 0.5% of a company's equity"), then enumerates the three query shapes it supports (one company, one investor, or both). An agent can distinguish this from holdings or insider tools without opening the schema.

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

Usage Guidelines5/5

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

Explicitly states the invocation constraint ("Pass at least one of symbol / name") and names two alternatives with the exact conditions that select them: get_shareholding_pattern for aggregate FII/DII/promoter holdings and get_insider_trading for promoter/KMP trades of any size. It also flags a misuse case ("Bulk deals miss gradual accumulation").

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