Skip to main content
Glama
Sign In

Equibles

by io.github.daniel3303
OverviewDiscussionsAdmin

Canadian ETF Holdings of a Stock

GetCanadianFundHoldings
Read-only

Get the Canadian exchange-traded funds holding one Canadian listing, written MIC:TICKER (e.g. XTSE:RY), from each fund's own newest published portfolio, largest position first: the fund's ticker and name, the portfolio's date, shares, value and the position's percentage of the fund. Each fund states its own date, some daily and others monthly. Only funds with a machine-readable portfolio are covered, and a fund that holds other funds is left out so the same shares are never counted twice. For US registered funds use GetFundsHoldingStock; for Swedish funds use GetEuropeanFundHoldings.

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": "GetCanadianFundHoldings"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoRows to skip for paging (default 0).
tickerYesCanadian listing symbol MIC:TICKER, e.g. XTSE:RY. A bare ticker names a US listing and is answered with the company's Canadian listings.
maxResultsNoMaximum funds, largest position first (default 20; max 100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare a safe read, so the description focuses on what the annotations cannot say: each fund reports from its own newest published portfolio on its own schedule (some daily, some monthly), fund-of-funds are dropped to avoid double counting, and results are ordered largest position first. That is exactly the behavioral context an agent needs to interpret dates and gaps in results.

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 action and scoping before coverage caveats and sibling routing. The first sentence is long and enumerates return fields in a dense list, but no sentence is wasted and nothing feels padded.

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?

No output schema exists, and the description compensates by enumerating the returned fields (fund ticker and name, portfolio date, shares, value, percentage of fund). Combined with ordering, date variability, and coverage limits, an agent knows what it will receive and where gaps come from.

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 baseline is 3. The description adds meaning beyond the schema by tying maxResults to the 'largest position first' ordering and reinforcing that the ticker denotes a single Canadian listing; however it repeats the MIC:TICKER example already present in the schema and says nothing about offset/paging.

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 ('Get the Canadian exchange-traded funds holding one Canadian listing') with the exact identifier format, and explicitly names the two sibling tools it is not (GetFundsHoldingStock, GetEuropeanFundHoldings). An agent can route on the first clause alone.

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?

Names alternatives and the condition selecting each: US registered funds go to GetFundsHoldingStock, Swedish funds to GetEuropeanFundHoldings. It also states the required MIC:TICKER form. Coverage exclusions (only machine-readable portfolios, fund-of-funds omitted) further bound when results will be empty.

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

All Equibles 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