Skip to main content
Glama
screener-mcp
by LogeshR15

get_shareholding_pattern

Read-only

Retrieve eight quarters of shareholding data—promoter, FII, DII, government and public percentages, trends, pledge severity and promoter-group checks—to analyze ownership shifts and risks.

Instructions

Shareholding pattern for the last 8 quarters, with the analysis:

  • rows: Promoter / FII / DII / Government / Public %, shareholder count

  • trends: per category — latest %, change over the window and over the last quarter (pp), direction

  • promoter_group: present or not. Companies like ITC have no promoter; promoter-trend and pledge checks then don't apply, and the response says so instead of implying "no pledge".

  • pledge: % of promoter holding pledged, from Screener's analysis, with severity (>50% high, 20-50% moderate, >0-20% low); not_flagged (none flagged — small pledges may not be); or not_applicable (no promoter)

symbol: NSE/BSE symbol

Examples: get_shareholding_pattern("ZEEL") get_shareholding_pattern("ITC")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_shareholding_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial behavior beyond the read-only and open-world annotations: it explains the row categories, trend calculations, promoter-group absence handling, pledge severity thresholds, and caveats such as small pledges not being flagged.

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?

Front-loads the purpose, uses a compact bullet structure for the returned analysis, and includes only relevant caveats and examples. The detail is proportionate to the tool's analytical scope.

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?

Despite an output schema being present, the description still defines the result structure and edge cases clearly. It covers the single parameter, promoter absence, and pledge interpretation, leaving no major ambiguity for invocation.

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 0%, so the description must carry parameter meaning. It identifies the symbol as an NSE/BSE symbol and gives concrete examples, though it does not specify case sensitivity or exchange-prefix conventions.

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?

States a specific verb and resource: retrieve the shareholding pattern for the last 8 quarters with analysis. The scope is clear, but it does not explicitly distinguish the tool from sibling research tools.

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?

Usage is implied by the tool's resource and scope, and examples are provided, but there is no explicit when-to-use guidance, exclusions, or comparison with alternatives such as insider trading or company overview tools.

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