Skip to main content
Glama

Tapetide - Indian Stock Market MCP

Shareholding Pattern

get_shareholding
Read-onlyIdempotent

Get shareholding pattern — promoter, FII, DII, public holdings over time. Track institutional buying/selling trends quarter over quarter. Useful for understanding ownership changes. detail=institutions: DII split (mutual funds, insurers, banks, pension funds, AIFs...) and FPI holder counts by quarter. CAUTION: a move of more than 5 points in any bucket in a single quarter may be a filing reclassification rather than trading. When you see one, report the public/other buckets for the same quarters alongside it and do not describe the move as accumulation or exit without a second source.

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

Input Schema

NameRequiredDescriptionDefault
typeNoPeriod type. Omit for all.
cursorNometa.next_cursor, with detail.
detailNo12 quarters per call, newest first.
symbolNoREQUIRED. The stock symbol, e.g. "RELIANCE" or "TCS".
tickerNoAlias for `symbol`.
identifierNoAlias for `symbol`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "meta.next_cursor, with detail.",
      +  "type": "string"
      +}
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "12 quarters per call, newest first.",
      +  "enum": [
      +    "institutions"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral value beyond that: it explains the detail=institutions expansion (DII sub-buckets, FPI holder counts) and, critically, warns that a >5-point bucket move may be a filing reclassification rather than trading, with a required reporting action. It does not mention pagination or return shape, but the annotations set a lower bar.

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 purpose, then detail semantics, then a clearly flagged CAUTION. Sentences are dense but each carries content; the CAUTION paragraph is longer than typical but justified by the misinterpretation risk it guards against.

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?

With six parameters, no output schema, and a cursor-based pagination scheme, the definition covers what the tool returns (ownership buckets over quarters) and the main analytical pitfall. Gaps remain around pagination mechanics and the alias parameters, which the schema handles but the description never reinforces.

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?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by spelling out what detail=institutions actually yields (mutual funds, insurers, banks, pension funds, AIFs, FPI holder counts). It does not address the symbol/ticker/identifier alias trio or the quarterly/annual distinction, leaving those entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ("Get shareholding pattern") and enumerates the returned buckets — promoter, FII, DII, public — plus the time dimension. It clearly differs from market-wide siblings like get_fii_dii_flows, but it never names an alternative, so sibling differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Useful for understanding ownership changes" and "track institutional buying/selling trends" imply the use case but give no when-to-use/when-not conditions and no comparison to adjacent tools such as get_fpi_sectors or get_fii_dii_detail. The CAUTION block is guidance on interpreting results, not on tool selection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.