Skip to main content
Glama

Indexes

list_indices
Read-onlyIdempotent

Use when someone asks how many memecoins launched on pump.fun, what memecoin launchpads earned in fees, how much traded on Kalshi and Polymarket, how many Americans filed first jobless claims, or what the US jobs number, unemployment rate, CPI or core CPI was when first published, before the Bureau of Labor Statistics revised it. Tickerz reads each as an index against its own normal (daily, weekly for LAYOFFS, monthly for JOBS, UNEMP, CPI and CORECPI), each reading timestamped in Bitcoin so it cannot be changed afterward. Every Tickerz Index: what it counts, its source, the newest day, the Activity score and signed z of the newest complete day, and the last 30 complete days as period, value and band. For a finished period read latest_complete. latest is the newest period on file; when it has provisional true it is a partial UTC day still counting, marked partial_day true, and its change_pct (also given as partial_change_pct) compares that partial day with a full one, so it is not a full-day change. Some sources land late (jobless claims about ten days after the week ends, Chicago crime over about a week), so latest_complete can be days behind today. Same data as GET /api/indices. A source whose terms keep its levels out of the API is served with its score and bands only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds substantial context they cannot: readings are timestamped in Bitcoin and immutable, provisional periods carry partial_day/partial_change_pct that are not full-day changes, sources can land late (claims ~10 days, Chicago crime ~a week), and some sources expose only score and bands due to terms. These are exactly the operational caveats an agent needs to avoid misreporting a number.

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?

The usage framing is front-loaded, which is good, but the opening sentence is a sprawling run-on list of example questions and the field/partial-day explanation packs several clauses together. The content earns its place, yet the density and length make it harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 must carry the return contract, and it does: enumerates the per-index fields, distinguishes latest from latest_complete, explains provisional periods, and flags reduced data for restricted sources. Minor gaps remain in that terms like 'band' and 'signed z' are used without definition, but an agent can still call and interpret the tool correctly.

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?

The tool takes no parameters, so there is no schema surface to compensate for; the description instead spends its words on the shape of the returned fields (period, value, band, z, change_pct). Baseline of 4 applies for a zero-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this tool surfaces every Tickerz Index with its counts, source, newest day, Activity score, signed z, and 30 days of period/value/band history, and it notes it is the same data as GET /api/indices. What it never does is state the operation crisply as a list-all against a single-index read, so an agent must infer the contrast with the sibling get_index.

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?

The opening 'Use when someone asks…' clause gives concrete triggering questions (pump.fun launches, Kalshi/Polymarket volume, jobless claims, CPI), which is strong when-to-use guidance. It also explains when to prefer latest_complete over latest and warns that late-landing sources can lag by days, but it never names an alternative tool such as get_index for single-index lookups.

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