Skip to main content
Glama

Tickerz

by com.tickerz
OverviewDiscussionsAdmin

Terminal

board
Read-onlyIdempotent

Use when someone asks what is unusual in crypto or US stocks right now, which coins trade far above their normal volume today, or how many are moving at once. Current Tickerz Terminal: all tracked assets with the 24h move, the activity score as score (0-100; score_1h is one hour earlier) and vol_mult (24h volume over the asset's 30-day baseline mean, measured), plus updated_at and breadth. assets mixes crypto and US stocks in one list sorted by score, so the first rows may be stocks: send class crypto or equity to get one kind, or filter on each asset's class. breadth counts crypto only, whatever class is sent: unusual is how many scored crypto assets are at 70 or more right now, scored counts the crypto assets with a score (an asset still building its 14 day baseline has score null and is not counted), and band is the study's band for the share: lone under 3% (so 0 unusual also reads lone), mid between, crowd at 30% or more. Same data as GET /api/board. heat and heat_1h are deprecated aliases of score and score_1h, same values, kept until at least 2026-12-31. No prices: they come from licensed vendors whose terms do not allow passing them on; tickerz.com shows them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
classNoOptional: crypto or equity (US stocks and listed funds). Leave out for every asset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / class
      Added value: +{
+  "description": "Optional: crypto or equity (US stocks and listed funds). Leave out for every asset",
+  "enum": [
+    "crypto",
+    "equity"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it discloses non-obvious traits: assets are mixed crypto+equity sorted by score, breadth counts crypto only regardless of class, score is null for assets still building a 14-day baseline, heat/heat_1h are deprecated aliases kept until 2026-12-31, and no prices are returned due to vendor licensing.

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?

Front-loaded with the use case before the field details, and every clause carries information given there is no output schema. It is dense and parenthetical-heavy, which slightly hurts readability, but nothing is truly 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?

With no output schema, the description must carry return-value semantics, and it does: score/score_1h scale, vol_mult definition, updated_at, breadth bands (lone/mid/crowd), and the null-score rule. An agent has everything needed to call and interpret it.

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 enum is already documented, but the description adds real meaning: the default (omit for every asset), the fact that mixing happens by default, and that breadth ignores the class filter. It goes beyond the schema baseline.

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 opens with concrete trigger scenarios (unusual crypto/US stock activity, coins far above normal volume) and then names the resource precisely: 'Current Tickerz Terminal: all tracked assets with the 24h move...'. It is unmistakably a market-anomaly board, distinct from asset, arena, or get_index siblings.

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?

Explicit when-to-use is given via the opening scenarios, plus guidance on the class filter ('send class crypto or equity to get one kind, or filter on each asset's class'). It does not name alternative tools or state when-not-to-use, so it stops short of a 5.

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

All Tickerz toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources