Skip to main content
Glama
tearsheet

tearsheet

by kewonit

get_ownership

Read-only

Retrieve a company's quarterly shareholding pattern, including promoter, institutional, and public holdings, shareholder counts, period changes, and named holders above 1% for ownership analysis.

Instructions

Get a company's shareholding pattern by quarter.

Returns promoter, institutional and public holdings in percent, the number of shareholders, and each row's change over the last period. Concise gives categories. Full adds the named holders that companies must disclose above 1%. Use it for questions about who owns a company or how ownership is changing.

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": {
      "company": "<company>"
    },
    "name": "get_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoconcise
companyYes
periodsNo

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofNo
unitsNo
entityNo
sourcesNo
warningsNo
next_cursorNo
retrieved_atNo
verificationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the bar is lower. The description adds useful disclosure of what comes back (percent holdings for promoter/institutional/public, shareholder count, period-over-period change) and what the detail levels expose. It stops short of noting limits such as how far back data goes or how periods interacts with quarters.

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 core action, then returns and usage. Four sentences, all earning their place, though the detail-level sentence mixes output description with parameter guidance in a slightly roundabout way.

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?

For a 3-parameter read-only lookup with an output schema (so return values needn't be explained), the description covers purpose, return shape and usage well. The unexplained periods parameter is the only substantive hole; the output schema covers the return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning; it explains the concise/full enum well (categories vs. named holders above 1%), which is the highest-risk parameter. The periods parameter is never explained, and no parameter descriptions exist in the schema to fall back on, leaving that gap unaddressed.

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?

Specific verb plus resource plus granularity: "Get a company's shareholding pattern by quarter." An agent can immediately tell this is the ownership-lookup tool, distinct from the metrics/financials siblings, without opening a schema.

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?

Explicitly frames the question types it answers: "who owns a company or how ownership is changing." That is real when-to-use context, but no exclusion or alternative is named (e.g., when to prefer a filing search for ownership detail), which keeps it short of a 5.

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