Skip to main content
Glama

Index

get_index
Read-onlyIdempotent

Use for the history, rules, source and proof of one index named by list_indices (GOON, LONELY, TILT, BROKE, STRAPPED, LASTCALL, OD, AIGF, SHELTER, SAD, SURRENDER, DARKWEB, PWNED, ZERODAY, BOOM, COE, ROADKILL, POTHOLE, JUNKER, LEAF, ICE, EVICTED, TAXMAN, TENTS, EBT, COYOTE, UNDERWATER, TAG, SPIN, PARLAY, KENO, BITE, DUMP, ROBOCAR, STRAY, ROCKS, FLYBY, BIGQUAKE, PPM, KPSTORM, LAYOFFS, YESNO, TRENCHES, MINTS, JOBS, UNEMP, CPI, CORECPI). JOBS, UNEMP, CPI and CORECPI are monthly, from the Bureau of Labor Statistics: a day's value is the Bureau's figure now, its settlement_value is the first print Tickerz read at release, and a month loaded as history carries a note and no settlement_value. One Tickerz Index: its definition, every period in its read window with its band and signed z, the first print of the newest complete period, the open round, past rounds, and the newest proof. latest_complete is the finished period; a provisional latest is a partial UTC day (partial_day true), and its change_pct, also given as partial_change_pct, is not a full-day change. For what is on-chain, read proof: covers_period and covers_value are the newest period of this index a proof holds and its value there, stamped_on is the UTC day that proof was stamped, with digest_sha256, bitcoin_height, proof_url (the exact text hashed, as JSON) and ots_url (the OpenTimestamps file), status (on_chain, awaiting_bitcoin, none or unavailable), and latest_complete with on_chain true or false. A live source's day is complete at 00:00 UTC and goes on-chain in the next day's proof, stamped after 12:00 UTC, so stamped_on is a day after covers_period and the newest complete day is often not on-chain yet. seal is the newest daily proof for every index: seal.day is the day it was stamped, not a period of this index. first_print is for latest_complete and stays null until a proof holds it. forecast is Forecast v1 for the next period: p10, p50 and p90 (an 80% range and its middle), the model the daily run chose, backtest (periods walked forward, coverage_80, skill_vs_last_number: the share of error removed against repeating the last number, negative when worse) and the live record; display only, never a settled number, null when none. Same data as GET /api/indices/{ticker}, plus proof. Levels a source's terms keep out of the API are null.

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

Input Schema

NameRequiredDescriptionDefault
tickerYesIndex ticker without the dollar sign, e.g. MINTS or YESNO

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Index ticker without the dollar sign, e.g. MINTS or GOON"New value: +"Index ticker without the dollar sign, e.g. MINTS or YESNO"
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only and idempotent, and the description goes well beyond them: it explains null semantics ('levels a source's terms keep out of the API are null'), partial-day behavior, the 00:00 UTC completion and 12:00 UTC stamping lag between a day and its proof, and that seal.day is a stamp day not a period of this index. It also warns that forecast is display-only and never a settled number — exactly the kind of trap an agent could fall into.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, but the 47-ticker parenthetical and the dense field-by-field prose make it a wall of text that is hard to scan. Much of the ticker list duplicates what list_indices already supplies, so it does not fully earn its space.

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 carries the full burden of explaining return values, and it does so thoroughly: periods with band and z, first_print, seal, proof fields with their status values, and forecast components including backtest metrics. An agent can interpret every part of the response from this text alone.

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% and the single parameter is already documented, so the baseline is 3. The description adds real meaning by tying the ticker to list_indices as the authoritative source and enumerating the valid ticker set, though it does not add format rules beyond 'without the dollar sign'.

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 opening sentence names the resource (one index) and its payload (history, rules, source, proof) and explicitly routes ticker discovery to list_indices, so the agent can separate it from list_indices without opening a schema. It also enumerates the exact ticker vocabulary, removing ambiguity about valid input.

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 clear context for use — call this after list_indices for a single index, and use proof for on-chain data — but never states an explicit when-not or names an alternative for the same data (e.g. a bulk variant). The 'Same data as GET /api/indices/{ticker}, plus proof' line usefully frames scope.

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.

Resources