Skip to main content
Glama
BlueWaterCorp

RiskModels

by BlueWaterCorp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

RiskModels ETF

riskmodels_get_etf
Read-only

Retrieve an ETF's registry metadata and portfolio snapshot, plus optional top holdings for exposure analysis and hedging.

Instructions

Use when you want one ETF's registry metadata and portfolio surface, and optionally its largest holdings. Not for finding an ETF ticker (use riskmodels_search) or the ETF's daily returns (use riskmodels_get_returns). Returns { snapshot, holdings }: snapshot from GET /data/etf/{ticker}; holdings, only when holdings_top is set, from GET /data/etf/{ticker}/holdings. Holdings follow the latest published holdings file; registry refreshed end-of-day. Free (no per-call charge).

Input Schema

NameRequiredDescriptionDefault
tickerYesETF ticker symbol, case-insensitive, e.g. SMH
holdings_topNoAlso return the largest N holdings, integer 1-200, e.g. 25 (default: no holdings)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.12
    • addedInput schema / properties / holdings_top
      Added value: +{
+  "description": "Also return the largest N holdings, integer 1-200, e.g. 25 (default: no holdings)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / ticker / description
      Previous value: -"ETF ticker, e.g. SMH"New value: +"ETF ticker symbol, case-insensitive, e.g. SMH"
  2. First observedv1.0.11

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover only the safety profile (readOnly/openWorld/non-destructive), and the description layers on traits they cannot express: the two backing endpoints, holdings sourced from the latest published file, registry freshness at end-of-day, and cost ('Free, no per-call charge'). Conditional output behavior is disclosed rather than left to inference.

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?

Three sentences, each earning its place: scoping first, exclusions second, return shape and freshness third. The endpoint URLs are dense but add provenance value rather than padding.

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 no output schema, the description still declares the return envelope ({ snapshot, holdings }) and when each component appears. For a two-parameter read tool with full annotation coverage, nothing needed to invoke it correctly 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 meaning beyond the schema by tying holdings_top to the presence of the holdings key in the response. It does not restate the 1-200 bound or case-insensitivity, which are already in the schema.

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 ('one ETF's registry metadata and portfolio surface, optionally its largest holdings') and explicitly separates itself from sibling tools riskmodels_search and riskmodels_get_returns. An agent can pick it out of a 23-tool family without opening a schema.

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?

Opens with an explicit when-to-use clause and adds two named exclusions with the correct alternatives for each case (ticker lookup -> riskmodels_search, daily returns -> riskmodels_get_returns). The conditional trigger for holdings (only when holdings_top is set) is also spelled out.

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