Skip to main content
Glama
Sign In

TickerDB

by com.tickerdb
OverviewDiscussionsAdmin

get_funds

Read-only

Find funds (ETFs and mutual funds) that publish holdings to the SEC on Form N-PORT, by name words or ticker, largest first. Each fund has fund_id (SEC series id), tickers, is_etf, its first and newest public portfolio dates. Then use get_fund_holdings for a portfolio, or held_by in get_universe / get_search. Names, tickers and sizes are current, not point in time. Costs 1 credit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_funds"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWords of the fund's name, any order, e.g. "ark innovation" or "core s&p 500".
limitNoRows per page, default 20, max 100.
offsetNoPaging offset, default 0.
tickerNoA fund ticker (e.g. "IVV", "VFIAX") or SEC series id ("S000004310").
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.6/5.0
Behavior5/5

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

Annotations already cover the read-only/safe profile; the description adds context they cannot: cost ('Costs 1 credit'), a temporal caveat ('Names, tickers and sizes are current, not point in time'), the sort order, and the fields each result carries. This is meaningful behavioral disclosure beyond 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 scoping, then the handoff, then caveats and cost. Dense and mostly waste-free, though the middle sentence enumerating every returned field is long and slightly crowds the routing guidance.

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 an output schema present, return values need not be spelled out, yet the description still names the key fields, sorting, cost, and temporal semantics. Nothing an agent needs to select or call this tool correctly is missing.

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 coverage is 100% and each parameter (q, limit, offset, ticker, etf_only) is already documented with examples. The description only echoes 'by name words or ticker' and the 'largest first' ordering, adding little meaning beyond the schema, so the 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?

States a specific verb and resource ('Find funds (ETFs and mutual funds) that publish holdings to the SEC on Form N-PORT'), plus search modes ('by name words or ticker') and default ordering ('largest first'). It is immediately distinguishable from siblings like get_fund_holdings and get_universe, which it names.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Then use get_fund_holdings for a portfolio, or held_by in get_universe / get_search.' This tells the agent what this tool hands off to and under which condition, which is exactly the when/when-not guidance needed.

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