Skip to main content
Glama
Sign In

TickerDB

by com.tickerdb
OverviewDiscussionsAdmin

get_fund_holdings

Read-only

A fund's full portfolio as public on one date (SEC Form N-PORT), largest positions first: every line as filed (stocks, bonds, cash funds, derivatives) with ticker (TickerDB symbol on that date when the CUSIP maps to an asset we cover, else null), cusip, isin, balance, value_usd, weight_pct (percent of net assets), asset_category (EC = common stock). Point in time: filing.filed_on is when the portfolio became public and filing.report_date the quarter end it describes (typically 2-5 months before the date). Coverage starts with the fund's first N-PORT (late 2019). Costs 1 credit plus 1 per 100 lines 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": {
      "fund": "<fund>"
    },
    "name": "get_fund_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD (default today). History depth depends on plan.
fundYesFund ticker (e.g. "IVV", "ARKK", "VFIAX") or SEC series id; find with get_funds.
limitNoLines per page, default 500, max 5000.
offsetNoPaging offset, default 0.

Output Schema

NameRequiredDescriptionDefault
dataNoThe TickerDB API response payload for this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only and open-world safety, and the description layers on non-obvious behavior: a credit cost model (1 credit plus 1 per 100 lines beyond 100), the ordering guarantee, null-ticker semantics when a CUSIP is uncovered, and the filed_on vs report_date distinction. These are costly surprises an agent could not infer from structured fields.

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 purpose, and no sentence is filler; the cost and coverage notes are genuinely useful. The heavy nesting of parentheticals makes it dense to parse in one pass, which keeps it from a 5.

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?

Even though an output schema exists, the description still explains the key returned fields (ticker, cusip, value_usd, weight_pct, asset_category), plus coverage limits and cost. Nothing needed to call it correctly or budget for it is missing.

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 100%, so the baseline is 3, but the description adds real meaning to the date parameter by explaining that report_date is the quarter the portfolio describes rather than the date it became public. The rest of the parameter text is left to the schema, which already documents fund, limit, and offset well.

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?

Names the exact resource (a fund's full SEC Form N-PORT portfolio on one date) and its ordering (largest positions first), plus the line-level contents. That is clearly distinct from the sibling get_fund_holders, which concerns who owns the fund rather than what it owns.

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?

Gives strong context for when this is the right tool: point-in-time snapshots, coverage starting late 2019, and the fact that the returned quarter end typically lags the public date by 2-5 months. It never explicitly names an alternative or a case where this tool is the wrong choice, so it stops 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.

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