get_bulk_deals
Retrieve recent bulk deals on NSE to track large transactions and analyze market movements.
Instructions
Get recent bulk deals on NSE.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieve recent bulk deals on NSE to track large transactions and analyze market movements.
Get recent bulk deals on NSE.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states 'recent', which is vague and does not disclose data volume, frequency of updates, or any potential limitations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, clear sentence with no extraneous information. It is concise and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no parameters and no output schema, the description is adequate but minimal. It could be improved by clarifying what 'recent' means (e.g., time frame) or what data fields are returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the baseline is 4. The description does not need to elaborate on parameters, and it correctly implies no input is required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and the resource 'recent bulk deals on NSE'. It is specific and distinguishes from sibling tools like get_block_deals which deals with block deals.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies use when needing bulk deals, but does not provide explicit when-to-use or when-not-to-use context, nor does it compare to alternatives like get_block_deals or get_nse_announcements.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/icharshal/india-market-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server