Skip to main content
Glama

Grok Crypto Quant API

Point-in-time top-N coin universe

universe_snapshot
Read-onlyIdempotent

Survivorship-free top-N coin list for any past date: Coinbase USD pairs ranked by trailing 20-day dollar volume using only data available that day. Fixes your own backtests: picking today's top coins hides the ones that died and overstates returns. Price: $0.05 USDC per call (x402, Base mainnet). Free pre-check: validate_universe.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD
top_nNo
min_age_daysNo
min_avg_dollar_volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive). The description adds what annotations can't: the ranking methodology (trailing 20-day dollar volume, data available that day only), the selection intent (survivorship-free), and pricing ($0.05 USDC per call via x402 on Base mainnet). It doesn't mention pagination or exact return shape, though no output schema exists, so a slight gap remains.

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?

Three front-loaded sentences: what it returns, why it matters, and cost/pre-check. No fluff, though pricing details could be separated, but it earns its place for an agent budgeting calls.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, read-only analytical tool with no output schema, the description is reasonably complete on methodology and pricing. However, it leaves parameter meaning (min_age_days, min_avg_dollar_volume) and return structure unaddressed, which is material given 25% schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only 'date' has a description 'YYYY-MM-DD'). The description mentions top-N and trailing 20-day volume but never explains top_n, min_age_days, or min_avg_dollar_volume, nor their defaults/limits. With low coverage, more compensation is expected.

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-equivalent (returns a coin list), the resource (Coinbase USD pairs), and the differentiating scope: point-in-time, survivorship-free, top-N by trailing 20-day dollar volume. This is clearly distinguished from siblings like backtest and token_check.

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?

Explains the use case well (fixing backtests that use today's top coins) and points to validate_universe as a free pre-check, which is an explicit alternative/companion. It doesn't state when NOT to use this tool or when backtest's own universe handling suffices, but the intended context is clear.

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