MarketPulse MCP

nse_bulk_deals

Retrieve recent bulk and block deals on NSE, highlighting transactions exceeding 0.5% of total shares to track institutional activity.

Instructions

Get recent bulk and block deals on NSE.

Shows large transactions where quantity traded exceeds 0.5% of total shares. Useful for tracking institutional activity.

No arguments needed.

Examples: nse_bulk_deals() → Recent bulk/block deals

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": "nse_bulk_deals"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.0Aug 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the threshold rule (0.5% of total shares) and that no arguments are needed, adding meaningful behavioral context beyond the tool name. It doesn't describe output format or data freshness, but these are not critical for a simple read-only data fetch.

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?

The description is concise and well-structured: it opens with the primary action, adds a qualifier, suggests a use case, then gives an example. Every sentence contributes without redundancy.

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 no-argument, read-only tool with an output schema in place, the description covers the essential elements: what it does, the transaction threshold, the use case, and an example invocation. There is no missing information that would impede correct usage.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4. The description confirms this with 'No arguments needed' and provides an example call, which is sufficient given there is nothing else to explain.

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 clearly states 'Get recent bulk and block deals on NSE', using a specific verb and resource. It also explains the qualification threshold (quantity exceeding 0.5% of total shares), distinguishing it from quote or historical data tools like nse_quote or nse_historical.

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 explicitly mentions usefulness for 'tracking institutional activity', which provides clear context for when to use it. However, it does not name alternatives or explicitly state when not to use it, so it stops short of full exclusion guidance.

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

Deploy Server