Skip to main content
Glama
Sign In
openmarkets

openmarkets

by danchev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_fund_equity_holdings

Retrieve the list of equity holdings for a specified fund using its ticker symbol. Get detailed information about the stocks within any fund.

Instructions

Retrieve the equity holdings for a specific fund.

Args: ticker (str): The symbol of the fund.

Returns: list[FundEquityHolding]: List of equity holdings in the fund.

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_equity_holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. The description only states the basic action and return type, without disclosing any behavioral traits (e.g., pagination, data freshness, permissions). Minimal beyond the obvious.

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?

Description is short, clear, and front-loaded. Three sentences cover purpose, arguments, and returns with no waste.

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?

Given the presence of an output schema, return details are covered. However, the tool is simple but lacks usage guidance and behavioral transparency, leaving some gaps.

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 0%, so the description adds meaning by explaining 'ticker' as the symbol of the fund. However, it remains minimal and could be more specific (e.g., ETF or mutual fund ticker).

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?

The description clearly states the tool retrieves equity holdings for a specific fund, using a ticker parameter. The name and description differentiate it from bond, asset class, or top holdings siblings, but does not explicitly distinguish from get_full_holdings.

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?

No guidance on when to use this tool versus alternatives like get_fund_top_holdings or get_full_holdings. Lacks context for tool selection.

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

Deploy Server

Other Tools