Skip to main content
Glama
Sign In

TickerDB

by com.tickerdb
OverviewDiscussionsAdmin

get_fund_holders

Read-only

Which funds held a stock on one date (SEC Form N-PORT, point in time: each fund's newest portfolio filed by the date), largest positions first, plus the tracked indexes it belonged to (index_memberships) and totals over every holder (fund_count, fund_shares). Each fund's shares and value_usd are as of its own report_date, typically 2-5 months earlier. Costs 1 credit plus 1 per 100 funds beyond 100.

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": {
      "ticker": "<ticker>"
    },
    "name": "get_fund_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD (default today). History depth depends on plan.
limitNoFunds per page, default 100, max 1000.
offsetNoPaging offset, default 0.
tickerYesStock or ETF ticker, e.g. "AAPL" (former symbols resolve).
etf_onlyNotrue: only ETFs listed in TickerDB.

Output Schema

NameRequiredDescriptionDefault
dataNoThe TickerDB API response payload for this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the read-only annotations by explaining the N-PORT selection rule, the typical 2-5 month reporting lag, and the credit cost. These are material behavioral details an agent needs before calling.

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, then layers point-in-time caveats and cost in dense but useful sentences. Every sentence adds information relevant to correct selection or invocation.

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?

With annotations covering safety and an output schema covering return fields, the description supplies the remaining critical context: source, staleness, ordering, totals, and cost.

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?

The schema already documents all five parameters at 100% coverage, but the description adds meaningful semantics for date: it explains that the date selects each fund's newest portfolio filed by then, not a live snapshot. It also ties limit indirectly to credit cost, though offset and etf_only remain schema-only.

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?

States a specific verb and resource ('Which funds held a stock on one date') and adds source and point-in-time semantics. The directional phrasing distinguishes it from the inverse get_fund_holdings lookup, even though the sibling is not named.

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?

The use case is implied clearly by the stock/date framing, but the description never explicitly says when to choose this over get_fund_holdings or other siblings, nor does it give exclusions.

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

All TickerDB toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources