Skip to main content
Glama

get_crypto_day_live

Read-only

Which crypto coins are in an uptrend right now, across the full board? The crypto book's day lane: where each coin stands right now, read under the same daily gate. The FULL 24/7 crypto day-state board: all 81 Robinhood-tradable coins with trend distances (20/50/200-day), multi-timeframe tape lights, ATR%, relative strength vs BTC, room to the 20-day high, volume z-score, mechanical UP/CHOP/DOWN state and cross-sectional ranks, plus the daily BTC/ETH gate and breadth. Publishes about every 5 minutes, 24/7. A state map, not a ranking. Live version. Coil Live is a subscription with a 7-day free trial; subscribers connect the Coil Live connector and sign in, and this read returns live data. Agents with an x402 wallet can also pay per call. Without a subscription or an x402 wallet it returns a PaymentRequired object and no data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the ~5-minute publish cadence, 24/7 availability, the subscription-plus-connector auth path with its 7-day trial, the x402 pay-per-call alternative, and the failure mode (returns a PaymentRequired object with no data). The refresh cadence also explains why idempotentHint is false despite readOnlyHint being true. This is the kind of context an agent needs to avoid a pointless or failing call.

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 a direct question that frames the purpose, then the scope, then the payload contents, then access terms. It is dense but the enumerated metrics earn their place because there is no output schema. The single unbroken paragraph and lists like 'multi-timeframe tape lights, ATR%, relative strength vs BTC' make it heavier 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.

Completeness5/5

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

With no output schema present, the description compensates by enumerating the returned fields, the gate/breadth context, and the ranking caveat. Auth, cadence, and the no-access return shape are all covered, leaving nothing an agent needs before calling.

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 zero parameters, so there is no per-parameter meaning to convey and the description cannot add syntactic detail beyond the empty schema. Baseline 4 applies.

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?

States a specific resource and scope: the full crypto day-state board covering all 81 Robinhood-tradable coins, read 'under the same daily gate.' It also draws a useful boundary ('A state map, not a ranking') and signals a live counterpart, so an agent can separate it from ranking-style siblings. It stops short of naming the non-live or night-lane siblings directly, which keeps it off a 5.

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?

Gives clear when-to-use context: for a current 24/7 snapshot of where every coin stands, not for ranked output. The 'Live version' phrasing tells the agent this is the real-time variant, and the access paragraph explains exactly what conditions must hold before a call is worthwhile. No explicit exclusion ('use X instead when...') is stated.

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