Skip to main content
Glama
icharshal

NSE-MCP

by icharshal

get_bulk_deals

Fetch today's NSE bulk deals where clients trade ≥0.5% of listed shares. Filter by symbol or deal type to view buyer/seller, quantity, and weighted-average price.

Instructions

Fetch today's NSE bulk deals — trades where a single client buys or sells ≥0.5% of a company's listed shares in one session. Returns the buyer/seller, quantity, and weighted-average price.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolNoFilter by NSE symbol (e.g. RELIANCE). Omit for all symbols.
dealTypeNoFilter by deal direction. Default: ALL.
Behavior3/5

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

No annotations provided, so description carries full burden. It indicates the tool is read-only and time-bound ('today's'), but lacks details like rate limits, data availability, or error conditions. Misses some behavioral traits.

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 sentences, front-loaded with key action, no extra words. Every sentence adds value.

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?

No output schema, but description lists returned fields (buyer/seller, quantity, price). For a simple tool, this is fairly complete; could mention pagination or limits.

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 100%, so baseline is 3. Description adds context about 'today's' but does not enrich parameter meaning beyond schema (e.g., date format for symbol filter).

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?

Description clearly states it fetches today's NSE bulk deals, explains the criteria (≥0.5% of listed shares), and distinguishes from siblings like get_block_deals. Verb is specific ('Fetch') and resource is well-defined ('NSE bulk deals').

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?

No guidance on when to use this tool vs alternatives such as get_block_deals or get_latest_bulk_deals. No explicit context on when not to use it or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/icharshal/NSE-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server