Skip to main content
Glama

Grok Crypto Quant API

Daily crypto market signals

market_signals
Read-onlyIdempotent

Daily crypto market regime in one call: BTC/ETH vs 20/50-day MAs, breadth of the point-in-time top-N (no survivorship bias), coins nearest a 20-day breakout, and the R1 breakout strategy's gate and entry signals. No candle fetching or indicator code. Completed UTC daily closes only. Price: $0.01 USDC per call (x402, Base mainnet). Free sample: signals_sample.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoUniverse size for breadth / breakout scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent safety, but the description adds genuinely new behavioral facts: paid access ($0.01 USDC via x402 on Base mainnet) and a data-freshness constraint (completed UTC daily closes only). Survivorship-bias handling is also disclosed. It stops short of describing response shape or failure modes, but the added context is substantial.

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 core value proposition and every clause carries information (components, cost, freshness, no local computation). The opening sentence is long and dense with comma-separated items, which slightly hurts scannability.

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?

No output schema exists, and the description compensates by enumerating exactly what comes back (MAs, breadth, breakout proximity, strategy signals). Cost, payment rail, and data-cutoff constraints are all stated, so an agent has everything needed to decide and call correctly.

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

Parameters3/5

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

The single parameter is fully documented in the schema (default 30, range 5-200). The description only adds a mild gloss via 'point-in-time top-N', which clarifies that the universe is historically accurate rather than today's list. Baseline 3 is appropriate since the schema carries the semantics.

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 resource (daily crypto market regime) and enumerates the exact components returned: BTC/ETH vs 20/50-day MAs, point-in-time breadth, breakout candidates, and R1 strategy gate/entry signals. That level of specificity clearly separates it from siblings like universe_snapshot or 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?

Explicitly frames it as a one-call bundle ('No candle fetching or indicator code') and points to signals_sample as a free sample, which gives the agent a clear alternative for cost-free trialing. It never states when *not* to use it, e.g. when raw per-coin data from universe_snapshot is preferable.

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