get_bulk_deals
Fetch recent bulk and block deals on the National Stock Exchange (NSE) to identify large transactions.
Instructions
Get recent bulk and block deals on NSE.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Fetch recent bulk and block deals on the National Stock Exchange (NSE) to identify large transactions.
Get recent bulk and block deals on NSE.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavioral traits. However, it only states the action without explaining what 'recent' means, whether data is real-time or delayed, or if any side effects exist. This leaves significant ambiguity for an AI agent.
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 unnecessary words. It is appropriately sized for a parameterless tool, though a bit more context would improve usability without harming conciseness.
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?
Given the tool has no parameters and no output schema, the description does not explain what constitutes 'bulk and block deals,' the format of the response, or the recency of data. This lack of contextual completeness may hinder an agent's ability to correctly interpret the tool's output.
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?
The tool has zero parameters, and the input schema with 100% coverage already clarifies that no input is needed. The description adds no parameter info, but the baseline for zero parameters is 4, and the description implicitly confirms no required input.
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 uses the specific verb 'Get' and clearly identifies the resource as 'recent bulk and block deals on NSE.' This effectively distinguishes it from sibling tools that deal with stocks, indices, mutual funds, etc.
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 that the tool should be used when the user wants bulk and block deals on the NSE, but it does not explicitly state when to use it versus alternatives or provide any exclusion criteria.
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/afthabvp/indian-market-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server