Skip to main content
Glama

get_crypto_night_live

Read-only

Which crypto coins have the strongest overnight momentum, across the full top five? The crypto book's overnight lane: one session-momentum read into the daily signal, with its study receipts. The FULL overnight continuation read: all top-5 session-momentum coins into the 20:00 UTC signal (81-coin Robinhood-tradable universe), the BTC 200-day regime gate state, the pre/post-signal phase clock, eligibility counts and the registered rule + study receipts (gross edge, null comparison, the retail-fee REFUTATION and breakeven bps, attached to every read). ~5-min refresh, 24/7. 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_night_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark readOnly/destructive=false and openWorld=true, and the description adds genuinely new behavioral facts: a ~5-minute refresh cadence, 24/7 availability, subscription-with-trial or x402 pay-per-call auth, and the explicit failure mode (a PaymentRequired object with no data). It does not contradict the annotations, though it omits pagination/response-shape and the risk that idempotentHint=false implies repeated calls may cost again.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

With no parameters and no output schema, the description carries the full burden, and the sentences are front-loaded with what the read returns. Some marketing phrasing ('study receipts', 'the retail-fee REFUTATION') is verbose but still conveys content.

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?

For a zero-param, no-output-schema tool it covers a lot: what is returned (top-5 coins, BTC 200-day regime gate, phase clock, eligibility counts, rule and study receipts), refresh cadence, and access/failure behavior. What remains thin is the shape of the receipts and how the per-call payment interacts with the non-idempotent hint.

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 are no parameter semantics to document and the baseline of 4 applies. The description's detail is about returned content, not inputs.

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 opening question and 'The FULL overnight continuation read: all top-5 session-momentum coins into the 20:00 UTC signal' do convey a specific resource and scope. It is clearly the overnight read and 'Live version.' flags it against the non-live sibling, though it never names that sibling or the day-lane alternative, and the 'crypto book's overnight lane / study receipts' jargon blurs the statement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It signals this is the 'FULL' read (implying a narrower counterpart exists) and gives concrete access guidance: subscribe to Coil Live or pay per call via x402. However, it never states when to pick get_crypto_night over get_crypto_night_live or how it differs from get_crypto_day_live, so the selection logic is left to inference.

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