Skip to main content
Glama

CoinRithm Agent Trading

TradFi reference prices

tradfi_references
Read-only

Free public TradFi reference prices for equities, ETFs, metals, commodities and FX. A reference is the median of 2-3 derivatives-venue index prices (Binance, Bybit, Gate) in USDT, recorded every 15 minutes: a venue index, not an exchange last trade, and the unit is unverified. live is a near-real-time overlay (null when unavailable); freshness is collection time. Omit ticker to page the catalog (latest, 24h/7d change, 24h range, live, key fundamentals). Pass ticker for one instrument with venue constituents, SEC fundamentals, corporate events and history over window, sampled to maxPoints. No API key required.

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

Input Schema

NameRequiredDescriptionDefault
limitNoList only: rows, 1-250 (default 25).
offsetNoList only: pagination offset (default 0).
tickerNoCatalog ticker such as AAPL or XAU. Omit to list.
windowNoDetail only: history window (default 24h).
maxPointsNoDetail only: history points, 2-1000 (default 100).
assetClassNoList only: one asset class.

Output Schema

NameRequiredDescriptionDefault
okYes
bodyNo
httpStatusYes
ledgerStatusNo
ledgerEventIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds critical provenance the annotations cannot: reference values are venue-index medians in USDT with unverified units, the data is collected every 15 minutes, freshness equals collection time, and 'live' is a near-real-time overlay that can be null. These are exactly the caveats that change how an agent should present or trust the data.

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?

Content is front-loaded with the data definition before the mode instructions, and every clause carries information (no filler or marketing). It is dense — long clauses packed into a few sentences — but nothing is redundant.

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?

For a read-only data tool with an output schema, the description covers everything needed to call it correctly: dual modes, unit and freshness caveats, an explicit null case for 'live', and what each mode returns at a high level. The output schema handles return formatting, so no return-shape detail 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 mode semantics the schema only hints at: ticker switching between catalog listing and single-instrument detail, and history over 'window' being downsampled to maxPoints. It leaves limit/offset and assetClass entirely to the schema, which is acceptable given full coverage.

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?

The description names the exact resource and coverage — 'TradFi reference prices for equities, ETFs, metals, commodities and FX' — and defines what a 'reference' is (median of 2-3 derivative-venue index prices in USDT, every 15 minutes) versus an exchange last trade. The dual list/detail behavior is spelled out by the omit-ticker vs pass-ticker split, so an agent knows precisely what it gets.

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?

It gives explicit mode-selection rules: 'Omit ticker to page the catalog' versus 'Pass ticker for one instrument'. It also flags that no API key is required. It stops short of naming alternative tools (e.g. crypto_price, get_candles) or stating when not to use this source, so 4 rather than 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.