Skip to main content
Glama

veroq_institutions

Retrieve institutional ownership data for any stock: top holders, shares, value, percent held, change, and filing date from 13F filings.

Instructions

Get institutional ownership data for a stock — top holders and ownership changes from 13F filings.

WHEN TO USE: To see which institutions own a stock and whether they're increasing or decreasing positions. RETURNS: Total institutional ownership %, summary stats, and top holders with shares, value, percent held, change, and filing date. COST: 2 credits. EXAMPLE: { "ticker": "AAPL" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker symbol (e.g. AAPL, NVDA, TSLA)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool consumes 2 credits and returns specific data, but it lacks details on update frequency, limitations, or any side effects. It mentions data source (13F filings) partially.

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?

The description is highly concise with separate sections for summary, when to use, returns, cost, and example. Every sentence is useful and earns its place, with no redundancy.

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 simple single-parameter tool without output schema, the description adequately covers purpose, usage, and return fields. It could mention pagination or ordering, but overall it is fairly complete.

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% for the single parameter 'ticker.' The description provides an example but does not add extra meaning beyond what the schema already provides (e.g., ticker format). Baseline 3 applies.

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?

The description clearly states it gets institutional ownership data for a stock, specifying 'top holders and ownership changes from 13F filings.' This is a specific verb and resource, distinguishing it from sibling tools like 'veroq_insider' or 'veroq_congress.'

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?

The 'WHEN TO USE' section provides clear context: 'To see which institutions own a stock and whether they're increasing or decreasing positions.' It does not explicitly state when not to use or name alternatives, but the guidance is sufficient.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Veroq-ai/veroq-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server