Skip to main content
Glama

FinanceQuery

Ownership and Insider Activity

get_holders
Read-onlyIdempotent

Get ownership data for a stock: major holders, institutional/fund ownership, or insider activity.

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>",
      "holder_type": "<holder_type>"
    },
    "name": "get_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum entries per page for holder types with a list (institutional, mutualfund, insider-transactions, insider-roster); omitted = curated default (25). No-op for major/insider-purchases (no list).
cursorNoOpaque continuation token from a previous response's `pageInfo.endCursor`; omitted = first page
fieldsNoComma-separated list of GraphQL field names to include; omitted = curated default set
symbolYesStock ticker symbol
holder_typeYesHolder type: major | institutional | mutualfund | insider-transactions | insider-purchases | insider-roster

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own — nothing about pagination shape, empty/missing data for a ticker, or how the six holder types differ in coverage or freshness.

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?

A single front-loaded sentence with no waste. It is appropriately sized, though the space saved could have been spent on the guidance that is currently missing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A five-parameter read tool with no output schema: the description should at least sketch what each holder_type returns and how pagination behaves across types. The schema covers the mechanics, but the semantics of the six holder types are left entirely to the caller.

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 100%, so the schema already documents limit, cursor, fields, symbol and holder_type, including the note that limit is a no-op for major/insider-purchases. The description's grouping of major/institutional/insider partially mirrors the enum but adds no meaning beyond it.

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 ('Get ownership data for a stock') and enumerates the data families it covers (major holders, institutional/fund ownership, insider activity), which an agent can map to the holder_type values. It does not distinguish itself from siblings such as get_congressional_trades or get_etf_profile, but the resource is narrow enough to be recognizable.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of when a different sibling should be preferred, and no explanation of how to choose among the six holder_type values that the schema exposes. An agent must infer everything from the parameter name alone.

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.