DalalOS: Indian Stock Market Research (NSE/BSE)

F&O participant activity

get_fo_participant_activity

Read-onlyIdempotent

Use this when the user asks how FIIs, DIIs, proprietary traders or clients are positioned in NSE futures and options across the whole market.

Get NSE participant-wise (FII/DII/Pro/Client) F&O open interest & volume — market-wide.

`days` (1..366, default 10) bounds the trailing window. Each row is one (trade_date,
client_type) pair with raw long/short contract counts across futures-index, futures-stock,
options-index-call/put, and options-stock-call/put, for both `oi` and `volume`.

This is a DIFFERENT, derivatives-side signal from `get_market_fii_dii_flow`
(market-wide daily CASH-segment net flow) — it is the highest-confidence official
substitute for FII/DII derivatives positioning (NSE's cash-market feed does not cover
F&O). Raw counts only — no "smart money"/positioning-bias interpretation (SEBI-RA line).

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

Input Schema

Name	Required	Description	Default
`days`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "additionalProperties": true,
-      "title": "Result",
-      "type": "object"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_fo_participant_activityOutput",
-  "type": "object"
-}New value: +null

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / days / default
```
Previous value: -30New value: +10
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "additionalProperties": true,
+      "title": "Result",
+      "type": "object"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_fo_participant_activityOutput",
+  "type": "object"
+}

First observedOct 27, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so safety is covered. The description earns extra credit by disclosing the row grain (one trade_date x client_type pair), the segments and both oi and volume, and a notable constraint: raw counts only with no positioning-bias interpretation. It omits freshness/lag and pagination behavior for larger day windows, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger sentence and the one-line purpose, then the parameter and row-shape details, then the sibling differentiation. It is somewhat long and the parenthetical asides (SEBI-RA line, cash-market feed caveat) add bulk, but each part carries information an agent would otherwise lack.

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?

There is no output schema, and the description fills that gap by describing the returned row grain, the contract segments and the oi/volume fields, plus the window semantics. Combined with annotations covering side effects, an agent has everything needed to select and call it correctly.

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% and the single `days` parameter has only a title and default. The description fully compensates by giving its valid range (1..366), the default (10), and its meaning as a trailing-window bound. That is exactly the missing semantics an agent needs.

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?

States a specific verb and resource: NSE participant-wise (FII/DII/Pro/Client) F&O open interest and volume, market-wide. It explicitly names the sibling it is not (get_market_fii_dii_flow, the cash-segment flow) and frames the data as the derivatives-side counterpart, so an agent can distinguish it from the many FII/derivatives siblings without opening schemas.

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?

"Use this when the user asks how FIIs, DIIs, proprietary traders or clients are positioned in NSE futures and options across the whole market" is an explicit trigger, and the contrast with get_market_fii_dii_flow clarifies the cash vs derivatives boundary. It does not address other nearby siblings such as get_derivatives_positioning, get_fii_activity, or get_stock_fii_flow, so the routing is clear but not exhaustive.

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

All DalalOS: Indian Stock Market Research (NSE/BSE) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.