Skip to main content
Glama
Sign In
The Stall

The Stall

by thebrierfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

etf-holdings

Retrieve top holdings, sector weights, and asset allocation for any US ETF. Provides up to 25 positions with weights, sector breakdown, and equity/bond/cash split.

Instructions

Top holdings, sector weights, and asset allocation for any US ETF (SPY, VOO, QQQ, AGG, XLK, etc.). Returns up to 25 positions with weights, sector breakdown, and equity/bond/cash split. No API key. $0.018/call.

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": "etf-holdings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerNoETF ticker symbol (e.g. SPY, VOO, QQQ, AGG, XLK, VTI). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations, but the description adds valuable behavioral context: returns up to 25 positions, sector breakdown, equity/bond/cash split, pricing, and no API key. Adequately discloses output structure and constraints.

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?

Two concise sentences, front-loaded with core purpose, followed by key details. No waste.

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?

Simple tool with one parameter and no output schema. Description fully covers return structure and usage constraints, making it complete for agent invocation.

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 covers 100% of the single parameter with description. Description adds value by listing example tickers and noting case-insensitivity, compensating for schema's minimal detail.

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?

Clearly states it retrieves top holdings, sector weights, and asset allocation for US ETFs. Specific verb+resource, and distinguishes from sibling tools like stock-price or equity-brief which serve different purposes.

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?

Provides example tickers and notes no API key required and cost, giving context. However, lacks explicit when-not or alternatives among sibling tools, though the scope is clear.

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